graze/config-validation

Its tiny audience and no commits in the past three months limit evidence of broad support. Unpinned CI actions and no security scanning are modest hygiene concerns, while the documented tests and release notes help offset them.

Latest 1.0.0

Packagist

76%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed for about 9 years but only four releases, with a median interval of about 308 days. A release within the last year shows it is not abandoned, though development is infrequent.

Repo commit activity

There were no commits and no active maintainers in the past three months. The recent release provides some counterevidence, but ongoing maintenance activity is currently thin.

Repo popularity

The repository has one star and no forks, indicating very limited public adoption. Popularity is only supporting evidence, so this lowers confidence in community support without making the package unfit.

Repo tooling

Composer and Make are used for project tooling, but no security-scanning tool was detected. The missing scanner is a modest transparency and hygiene gap.

Security policy

The repository has no security policy. This limits the project's stated process for receiving and handling vulnerability reports.