red-jasmine/permission

The package is small, clearly tied to its repository, and backed by an organization. Its zero recent commit activity, absent security policy, and lack of automated security tooling leave maintenance and oversight concerns.

Latest 1.0.13

Packagist

61%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Lifecycle scripts

The package uses a post-autoload-dump lifecycle script. This adds install-time behavior that merits awareness, but the signal alone does not establish unsafe or excessive behavior.

Release history

Ten releases arrived within the first few days, but no release has appeared since January 24, 2026; this suggests an immature release history with no demonstrated ongoing cadence.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. For a package released only a few days earlier, this is a meaningful warning that maintenance may have stopped.

Repo popularity

The repository has zero stars, forks, and watchers. This is weak supporting evidence, but the package is young and popularity alone does not determine health.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest oversight concern rather than a severe dependency risk on its own.