voodoo-rocks/yii2-user

The MIT license and two runtime dependencies keep adoption straightforward. Missing consumer documentation and security practices add friction, while the repository’s minimal project structure offers little evidence of ongoing engineering.

Latest 0.2.0

Packagist

32%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in April 2017, with no release in more than nine years. That is strong evidence of abandonment for a dependency receiving ongoing fixes.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving maintenance capacity un demonstrated.

Package scaffolding

The artifact has no README, which makes a library harder to integrate and understand. The absence of tests and a changelog is normal for published artifacts and is not counted against it.

Repo tooling

Composer is used for builds, but no security scanning tool is configured. This is a modest transparency and maintenance gap rather than evidence of an unsafe release.

Security policy

The linked repository has no security policy, leaving vulnerability reporting and response expectations unclear. Combined with the inactive project, this increases maintenance risk.