dmk/mkcleaner

Tests, a clear README, and organization backing provide useful maintenance context. The workflow configuration still needs careful review before adoption because its actions are unpinned and its release workflow contains a high-confidence finding.

Latest v13.0.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no releases in the last 12 months, despite a latest release on September 19, 2025. This indicates slowed maintenance, though the project is less than three years old and has seven releases overall.

Repo commit activity

There were no commits and no active maintainers during the last three months. Combined with no releases in the last 12 months, this is meaningful evidence of currently inactive maintenance.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and hygiene gap rather than evidence that the package is unsafe.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. The otherwise documented project and tests provide some compensation, but not a complete substitute.

Workflow audit

All 11 analyzed action references are unpinned, which weakens build reproducibility. The release workflow also has a high-confidence template-injection finding; without a dangerous trigger or untrusted checkout reported here, this remains workflow hygiene rather than a standalone severe risk.