zenstruck/bytes

Clear documentation, a matching MIT license, repository tests, and release notes make the package straightforward to evaluate. Organization backing and a minimal runtime dependency reduce adoption friction, while the small project footprint limits the significance of its modest popularity.

Latest v1.1.0

Packagist

69%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

100

Health Score Breakdown

Release history

The package has four releases over about three years, with one release in the last 12 months and intervals of about four months. This is slow but plausible for a small, focused value-object library.

Repo commit activity

The repository recorded no commits and no active maintainers in the last three months. For a small library this may reflect stability, but it leaves current maintenance capacity unproven.

Repo tooling

The project uses Composer, but no security-scanning tooling was detected. This is a modest transparency and maintenance gap rather than a standalone adoption blocker.

Workflow audit

The single workflow was fully analyzed with no injection, untrusted-checkout, or high-severity findings, but all six action references are unpinned. Unpinned CI dependencies weaken build reproducibility and supply-chain hygiene.