Use micromatch to filter npm module dependencies by name.
52%
Total Score
33
50
75
83
The package has 8 releases over roughly 14 years, but the latest release was in August 2017 and there were no releases in the last 12 months. That long release gap is a meaningful maintenance concern.
The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with the old last push and release, this is the main abandonment concern.
Four runtime dependencies are declared for this small utility, including micromatch and resolution helpers. This is a moderate dependency surface rather than an unusually heavy one, but it adds maintenance exposure to an old release.
The repository is owned by an individual account rather than an organization, so there is no visible organizational backing to compensate for the thin current maintenance activity.
There are no new issues or pull requests in the last month and one open issue. This indicates little current project activity, though the low issue volume is not itself severe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
resolve Version ^1.4.0 | — | — |
micromatch Version ^3.0.4 | — | — |
findup-sync Version ^2.0.0 | — | — |
stack-trace Version 0.0.10 | — | — |
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.