liberusoftware/audit

MIT licensing, clear documentation, tests, and a changelog provide a solid consumer and maintenance baseline. Organization backing and recent two-contributor activity help, though the project remains young and its workflow references need tighter pinning.

Latest 1.4.1

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is only 49 days old, despite 11 releases in that period, so its long-term maintenance record is not yet established. The rapid release activity is encouraging but does not remove the maturity gap.

Repo bus factor

Two contributors are active, but one made 80% of recent commits. The organization backing provides some ability to transfer maintenance, so this is a limited concentration concern.

Repo tooling

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

Security policy

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.

Workflow audit

All three workflows were analyzed cleanly with no audit findings or dangerous untrusted triggers, but all three action references are unpinned. This leaves routine build inputs less reproducible and harder to control.