godsboss/zebra

The package is small and easy to inspect, with tests, a README, a license, and no runtime dependencies. Its source repository shows no commits in the last three months, while the registry contains only one release from nearly six years ago. Adopt it only when its narrow, stable behavior fits your needs.

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 nearly six years ago, with no releases in the last 12 months. This leaves little evidence of sustained release maintenance, despite the package's small scope.

Repo commit activity

The repository has zero commits and zero active maintainers in the last three months. That is a meaningful maintenance warning for a package with only one historical release.

Repo popularity

The repository has one star and no forks, providing little community evidence or redundancy. Popularity is only supporting evidence, so this is a minor concern rather than a verdict.

Repo tooling

Composer is used for the build, which fits the package ecosystem, but no security-scanning tools are present. The missing scanning is a modest hygiene gap.

Security policy

The repository has no security policy. For a small utility this is a limited transparency gap, but it reduces clarity about vulnerability reporting and response.