Package Health/alireaza/dependency-injection

alireaza/dependency-injection

Usable with caveats: the package is licensed, tested, clearly linked to its repository, and not deprecated, but it has had no release or commit activity for about four and a half years. Its very small user and contributor footprint also makes long-term maintenance uncertain.

Latest 1.2.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only three releases and none in the last 12 months; its latest release was about four and a half years ago. This is a substantial maintenance and abandonment concern.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the long gap since the last release and increasing abandonment risk.

Project backing

The registry namespace and repository owner match, but the project is user-owned rather than organization-backed, so the single-person maintenance model remains a concern.

Repo popularity

The repository has zero stars and forks and only one watcher, offering little supporting evidence of adoption or community oversight.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. For a small library this is a transparency gap rather than evidence that the release is unsafe.