Package Health/draw/dependency-injection

draw/dependency-injection

Healthy and actively maintained, with a clear repository, frequent releases, and current contributor activity. Its small audience and lack of a security policy are modest transparency concerns, but the package is not deprecated or archived and includes tests.

Latest 0.43.0

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual account rather than an organization, so the small maintainer base and contributor concentration represent genuine continuity considerations.

Repo bus factor

One contributor made 80% of the recent commits, creating some concentration risk, but a second contributor remains active and the package has recent releases. The residual risk is modest.

Repo popularity

The repository has 0 stars and 0 forks, with 1 watcher, indicating limited external adoption. This is supporting caution rather than a health verdict because recent maintenance is active.

Repo tooling

Composer build tooling is used, but no security scanning tool is reported. The missing scanning is a transparency gap, though no other signal indicates unsafe maintenance behavior.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This lowers transparency but does not by itself indicate that the package is unsafe to adopt.