Package Health/berlioz/service-container

berlioz/service-container

This is a generally healthy and actively maintained release: it has a stable major version, six releases in the last 12 months, a recent repository push, an organization-owned source repository, an MIT license, and no registry deprecation or install-time lifecycle scripts. Adoption signals are modest, and recent repository activity is concentrated in one contributor, while the repository has no tests or security policy; these are meaningful transparency and continuity concerns, though the organization backing and continued release activity reduce abandonment risk.

Latest v3.2.1

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A README and changelog are present and the source repository uses GitHub Releases, but both the artifact and repository report no tests; this reduces visible validation coverage for a reusable service-container library.

Repo bus factor

All 3 recent commits came from one contributor, giving a 100% top-contributor share and creating continuity risk; the organization-owned repository provides some compensating handoff capacity but does not remove the concentration concern.

Repo popularity

The repository has only 1 star, 1 fork, and 3 watchers; this is weak supporting evidence for community scrutiny, but popularity alone is not decisive for a small library.

Security policy

No repository security policy was found, which weakens vulnerability-reporting transparency; the presence of Codacy scanning partially compensates but does not replace a documented policy.