dg/composer-cleaner
Its release cadence is deliberate rather than frequent, and the repository has no security policy or automated security scanning. A maintained source tree, passing test presence, recent release, and stable version offset those transparency and maintenance concerns.
68%
Total Score
50
86
50
Health Score Breakdown
The package has existed since January 2015 with 12 releases and one release in the last 12 months; the long median interval of about 251 days suggests deliberate, limited maintenance rather than abandonment, especially given the recent release.
There were zero commits and zero active maintainers in the last three months, a concrete sign that maintenance may be slowing, although the recent repository push and release provide some compensation.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest project hygiene gap.
The repository has no security policy, so there is no documented vulnerability-reporting process for users or maintainers.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 David Grudl |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 4 months ago
- Created
- 11 years ago
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.