mnshankar/repository

Its README, MIT license, and matching source repository make the package straightforward to inspect and identify. The prolonged absence of releases and repository activity leaves compatibility and support uncertain.

Latest v3.1

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no releases in the last 12 months, and its latest release was published about nine years ago. That prolonged inactivity is a substantial abandonment and compatibility concern.

Repo commit activity

The repository recorded zero commits and zero active maintainers over the last three months, consistent with the stale release history and providing no evidence of ongoing maintenance.

Maintainers

Only one registry account has publish access. That is a thin publishing base for an independently owned project and offers little resilience if the maintainer is unavailable.

Project backing

The repository is owned by an individual account rather than an organization, so there is no visible organizational backing to compensate for the single maintainer and long inactivity.

Repo tooling

Composer is used for the build, but no security-scanning tooling is present. This is a modest transparency and hygiene gap, not a severe risk by itself.