othercode/container

The package has a clear MIT license, tests, a focused file tree, and minimal runtime dependencies. Composer tooling and Dependabot provide some maintenance hygiene, but the small project footprint limits confidence in long-term support.

Latest v1.0.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published in October 2017, with no releases in the last 12 months. This is strong evidence of limited ongoing maintenance, although the linked repository was pushed more recently.

Project backing

The repository is owned by an individual rather than an organization, so the single registry maintainer does not have organizational backing to compensate for the limited maintenance activity.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the release-history concern and indicating no current development activity.

Repo popularity

The repository has one star and no forks, so there is little community evidence to supplement the thin maintenance history. Low popularity alone is not a decisive health problem for a small package.

Security policy

No security policy is present in the repository, leaving vulnerability-reporting guidance undocumented. This is a transparency gap, but it is not severe enough to outweigh the license, tests, and simple dependency profile.