maarky/singlecontainer

The package is small and easy to inspect, with a single runtime dependency and a clear README. Its lone maintainer and absent security scanning leave little evidence of ongoing support.

Latest 1.0.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in February 2018, with no release in more than eight years. This is strong evidence of abandonment risk despite the package reaching a stable 1.0.0 release.

Repo commit activity

There were zero commits and zero active maintainers during the last three months, consistent with the last push occurring in February 2018 and materially increasing abandonment risk.

Project backing

The package and repository are owned by the same individual account, so the source appears correctly aligned, but there is no organizational backing to offset the single-maintainer risk.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide no evidence of a wider maintenance community.

Repo tooling

The repository uses Composer, but no security scanning tools were detected. For a small library this is a modest transparency and maintenance gap rather than a standalone severe risk.