elliotjreed/gfs-tracking

The package has a clear README, tests, an MIT license, and a small runtime dependency set. Maintenance appears stalled, with no commits or releases for nearly two years, while the workflow uses unpinned actions and the repository has no security policy.

Latest 0.0.5

Packagist

48%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published nearly two years ago, and there have been no releases in the last 12 months. All five releases were clustered within about 24 minutes, suggesting an immature release history rather than sustained maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating that maintenance capacity may have lapsed.

Repo tooling

The project uses Composer and Make, but no security-scanning tools were detected. This is a meaningful transparency and maintenance gap for a package that handles API-related code.

Security policy

The repository has no security policy, leaving no documented path for reporting vulnerabilities or explaining how security issues are handled.

Workflow audit

The single workflow was fully analyzed with no dangerous triggers or audit findings, but all 3 action references are unpinned, so their code can change without a fixed version.