blaspsoft/forerunner

It has clear documentation, release notes, repository tests, and a security policy. The 0.x API is still evolving, recent commit activity is absent, and workflow actions are not pinned, so maintenance and build reproducibility remain concerns.

Latest v0.2.1

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

100

Health Score Breakdown

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. That is a meaningful maintenance and abandonment concern for a package consumers integrate into applications.

Release history

Seven releases were published within the last 12 months, showing active initial delivery, but the releases were concentrated around the project's first day rather than spread across the package's 335-day lifetime.

Repo issue activity

There was no new or closed issue or pull request activity in the last month, while one issue and two pull requests remain open. This supports the concern that current maintenance is inactive.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and hygiene gap, not evidence of an unsafe release by itself.

Version stability

The release is on the 0.x major line, and the README identifies the API as pre-release with possible changes before 1.0. This raises compatibility risk despite the registry not marking the specific version as a prerelease.