Minify blade format for personal use
58%
Total Score
50
93
50
Only one registry maintainer is listed, leaving limited observable publishing capacity for a user-owned project. This is a modest concern rather than a severe risk because the repository and package owner match.
The package has six releases but none in the last 12 months, with the latest published about five years ago. This is a meaningful maintenance concern, partly offset by the stable release history and an exact-version release note.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. This raises abandonment risk even though the project is not archived.
No security policy was found in the repository. That weakens vulnerability-reporting transparency, although it does not by itself show unsafe code or abandonment.
The single workflow was fully analyzed with no injection or high-severity findings, but both of its two action references are unpinned. This is a supply-chain hygiene gap without evidence of an exploitable workflow path.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
mrclay/minify Version ^3.0 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.