contenir/storage

This release appears generally healthy to depend on: it is actively released, not deprecated or archived, clearly licensed, well documented, and backed by a repository whose package identity matches the artifact. The repository includes substantial source and test coverage, and the organization ownership provides some maintenance continuity. The main concerns are that the project is still pre-1.0, all recent commits come from one contributor, and the repository has no security policy or security-scanning tooling; these warrant review for production adoption but do not indicate abandonment.

Latest v0.6.6

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

All 15 recent commits came from one contributor, creating a genuine continuity risk. Organization ownership provides some potential handoff capacity, but no second active contributor is shown by this signal.

Repo commit activity

There were 15 commits in the last 3 months, demonstrating active development, but only one active maintainer performed them all.

Repo popularity

The repository has zero stars, forks, and watchers, which provides little external validation. This is a supporting concern rather than a decisive health issue because the package shows strong release and test activity.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured. The missing security automation is a hygiene gap, not a standalone severe risk.

Security policy

The repository has no SECURITY.md or other detected security policy, reducing transparency around vulnerability reporting and response.