b13/menus

The package has clear licensing, a substantial README, repository tests, and an organization-backed source project. Recent commit activity is absent, while all three workflow actions are unpinned and a high-confidence template-injection issue was found. It remains maintained enough to consider, but warrants caution around updates and automation.

Latest 2.0.1

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. This is a meaningful maintenance warning, although the recent 2.0.1 release shows the project has not been abandoned outright.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. This is a hygiene gap rather than evidence that the release is unsafe by itself.

Security policy

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

Workflow audit

Both workflows were analyzed successfully, with no untrusted checkout or script-injection findings, but all 3 action references are unpinned. The high-confidence template-injection finding in publish.yml is a release-automation hygiene risk; template injection alone does not establish a severe dependency risk.