hectordev15/tenancy

The MIT license, included tests, clear README, and modest runtime dependency set improve transparency and adoption. Missing security scanning and policy leave fewer safeguards for a package with no recent maintenance.

Latest v1.1

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository recorded zero commits and zero active maintainers over the last three months. Combined with the old release, this materially increases abandonment risk.

Project backing

The repository is owned by an individual account rather than an organization, so the small two-person registry maintainer list is not offset by visible organizational backing.

Release history

The package has only one release, published nearly seven years ago, with no releases in the last 12 months. That is strong evidence of abandonment for a framework integration package.

Repo issue activity

There were no new or merged pull requests and no issue activity in the measured month. This supports the broader indication that the project is inactive.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap, especially for an inactive package.