cleup/guard

This is a generally healthy, actively maintained release: it is not deprecated or archived, has a recent push, regular releases over the past year, stable versioning, a small dependency footprint, clear MIT licensing, and repository activity from two contributors. The main reservations are the absence of tests and a changelog, no security policy or security-scanning tooling, zero repository popularity, and a relatively concentrated contributor share; these reduce transparency and resilience but do not outweigh the package’s recent release and commit activity. It appears reasonable to depend on, with normal caution appropriate for a security-focused package whose automated security assurance is limited.

Latest 1.0.14

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. This is a modest publishing-resilience concern, although repository activity shows a second active contributor and registry access does not measure actual maintenance participation.

Package scaffolding

A README and GitHub Releases are present, but neither the artifact nor repository contains tests or a changelog. For a security-focused package, the lack of tests is a meaningful maintenance and assurance gap, while releases partly compensate for the missing changelog.

Project backing

The repository is owned by an individual user rather than an organization, so there is no organizational succession or maintenance handoff evidence to offset the small maintainer base.

Repo bus factor

Two contributors were active in the last three months, but the top contributor made 75% of commits. The second contributor provides some continuity, yet maintenance remains concentrated.

Repo popularity

The repository has zero stars, forks, and watchers. This limits independent adoption evidence, but popularity is supporting evidence rather than a health verdict and does not outweigh observed maintenance.