tempest/container

This is a healthy, actively maintained release with strong recent release and commit activity, a stable major version, an unarchived repository, clear MIT licensing, and a modest runtime dependency profile. The repository is organization-owned and includes tests even though tests and a README are not packaged, which compensates for the artifact-level scaffolding gap. The main reservations are that 94% of recent commits come from one contributor, the repository has no security scanning or security policy, and repository popularity is very low; these are meaningful transparency and resilience concerns but do not outweigh the evidence of current maintenance and frequent releases.

Latest v3.19.2

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

Although four contributors were active, the top contributor made 46 of 49 recent commits, creating substantial contributor-concentration risk. Organization backing partly compensates because maintenance can be handed off within the project.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured; this is a moderate supply-chain transparency gap rather than evidence of abandonment.

Security policy

The repository has no documented security policy, reducing transparency around vulnerability reporting and response procedures.