sledgehammer/core

Its small dependency footprint, clear README, tests, and MIT license support adoption. Recent development appears uneven, and workflow references are not pinned; the missing security policy adds a smaller transparency concern.

Latest 26.03.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is a mature package, released for nearly 14 years with 47 releases, but only one release appeared in the last 12 months. That recent slowdown warrants caution despite the long history.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. The recent release and push show some current activity, but the lack of ongoing commit activity still lowers maintenance confidence.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and maintenance gap rather than evidence of unsafe code.

Security policy

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities.

Workflow audit

The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all three action references are unpinned, which weakens build reproducibility and supply-chain hygiene.