mika56/spfcheck

Clear documentation, tests, licensing, and release notes make the package straightforward to evaluate and integrate. Pin this release and verify future maintenance before upgrading, since recent project activity is absent.

Latest 3.0.1

Packagist

64%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed for about 10 years with 17 releases, but it had no releases in the last 12 months. This suggests slowing maintenance, though the long history and 121-day median release interval provide some maturity evidence.

Repo commit activity

There were no commits and no active maintainers in the last 3 months. This is direct evidence of currently quiet development and raises abandonment risk, even though the repository is not archived.

Repo issue activity

There were no new or closed issues or pull requests in the last month, while 7 issues and 2 pull requests remain open. This reinforces the picture of limited recent project activity.

Repo tooling

Composer is used as the build tool, but no security-scanning tooling was detected. The missing scanner is a modest transparency and hygiene gap, not evidence of unsafe code.

Security policy

The repository has no security policy. For a network-facing SPF library, this leaves vulnerability-reporting expectations unclear, although the package's tests and source transparency partly compensate.