find the closest .gitignore file, parse it, and apply ignore rules
57%
Total Score
38
100
78
88
50
The latest release was about 7 years and 6 months ago, with no releases in the last 12 months. Six total releases show some history, but the long publication gap materially raises abandonment risk.
The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with the old last push, this is strong evidence that maintenance has stopped.
No build attestation or trusted-publisher information is present. This limits publication transparency, though it is not by itself evidence that the release is unsafe.
One registry publishing account is a thin operational base, but the linked repository is owned by the same individual, so the evidence supports continuity rather than an unexplained ownership mismatch.
The repository is owned by an individual rather than an organization, so there is no organizational backing to offset the single-maintainer and inactivity concerns.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
find-up Version ^3.0.0 | — | — |
minimatch Version ^3.0.4 | — | — |
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.