sarehub/gcm

The package is small and easy to inspect, with a clear MIT declaration and a focused dependency set. Its documentation is present, but the project shows no recent maintenance and lacks tests, security scanning, and a security policy, making long-term reliance risky.

Latest 0.1.2

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only 3 releases, all clustered on 8 August 2019, with no releases in the last 12 months and an age of about seven years. This is strong evidence of abandonment risk despite the package not being registry-deprecated.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long release gap. No provided maintenance signal compensates for this inactivity.

Repo popularity

The repository has 0 stars, 1 fork, and 0 watchers, providing little supporting evidence of community adoption or external maintenance. Popularity is only supporting evidence, so this reinforces but does not determine the result.

Repo tooling

Composer is used for builds, which is appropriate, but no security scanning tools are present. This is a modest transparency and maintenance gap, not a severe risk by itself.

Security policy

The repository has no security policy or documented security contact. That weakens vulnerability-reporting transparency, although it does not establish that the package is unsafe.