berlioz/config

This is a generally healthy and actively maintained package: it has existed for over 6 years, has a stable major release, published five releases in the last 12 months, is not deprecated, and its linked organization-owned repository was recently updated. The main concerns are a very small observed contributor base, no repository tests, minimal repository popularity, and no security policy; these warrant caution but do not outweigh the consistent release activity, clear package/repository identity, licensing, build tooling, and organization backing.

Latest v3.2.1

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact and repository include a README and changelog, and the repository uses GitHub Releases, but neither contains tests. The documentation and release evidence compensate for the missing tests as a maturity gap, though test coverage remains unverified.

Repo bus factor

All three recent commits came from one contributor, producing a 100% top-contributor share and a low observed bus factor. Organization ownership provides some handoff capacity, but no second active contributor is evidenced.

Repo popularity

The repository has zero stars, one fork, and two watchers, indicating limited external adoption or visibility. Popularity is supporting evidence rather than a verdict, so this lowers confidence in ecosystem maturity without making the package unfit.

Security policy

The repository has no security policy. This is a transparency and vulnerability-reporting gap, though it is not by itself evidence that the package is unsafe.