internal/destroy

The project is small and its registry history is thin, while workflow references are all unpinned. Repository tests, release notes, licensing, and security tooling provide useful support, but the quiet recent commit window warrants pinning this exact version.

Latest 1.0.0

Packagist

67%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the only release, published 375 days ago, with no releases in the last 12 months. That thin history limits evidence of sustained maintenance, despite the stable 1.0.0 version.

Repo commit activity

There were no commits or active maintainers in the last 3 months. This is meaningful evidence of a currently quiet project and raises abandonment risk, although the repository was pushed about 7 months ago.

Security policy

No repository security policy was found. For a small package this is a transparency gap, though the presence of composer-audit partly offsets the missing process documentation.

Workflow audit

All 4 workflows were analyzed without failures and showed no dangerous triggers or audit findings, but all 12 action references are unpinned. That leaves avoidable build-integrity risk without evidence of an actively exploited workflow.