efrogg/archivemanager

Tests and a usable README provide some adoption support, while the single maintainer and absent security tooling limit ongoing oversight. The package has seen no releases or repository commits for about 10 years, so maintenance risk is substantial.

Latest v0.2

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The last release was about 10 years ago, with no releases in the past 12 months and only three releases overall. This is strong evidence of abandonment risk for a dependency that may need fixes or compatibility updates.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the past three months, consistent with the long release gap. No newer activity is provided to offset that maintenance concern.

Maintainers

The registry lists one maintainer, which creates a thin ownership base. The linked repository is user-owned rather than organization-backed, so no provided evidence compensates for the limited continuity.

Repo popularity

The repository has zero stars, one fork, and one watcher, offering little supporting evidence of broad review or community maintenance. Popularity is only supporting evidence, so this reinforces rather than determines the result.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. That leaves a transparency and maintenance gap, though it is less severe than the prolonged inactivity.