tms/consent

The organization-backed repository remains available and the package is clearly documented for consumers. MIT licensing, release notes, and a small dependency surface help, but maintenance and security visibility are limited.

Latest 1.3.0

Packagist

54%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest registry release was over four years ago, with no releases in the last 12 months. This is substantial evidence of slowing maintenance for a package consumers may still depend on.

Repo commit activity

The repository recorded no commits and had no active maintainers in the last three months, while its last push was over two years ago. The organization backing helps somewhat, but does not replace recent maintenance activity.

Repo issue activity

There were no new or closed issues or pull requests in the last month, alongside four open issues and 16 open pull requests. This suggests unresolved project activity rather than an actively maintained queue.

Repo popularity

The repository has one star, no forks, and one watcher, providing little supporting evidence of broad review or community involvement. Low popularity alone is not decisive, but it offers no compensating maintenance signal.

Security policy

The repository has no security policy, leaving disclosure and response expectations unclear. This is a transparency gap, though it is less severe than evidence of a compromised or abandoned source project.