resolve like require.resolve() on behalf of files asynchronously and synchronously
72%
Total Score
caution
Long-lived and actively released, but recent repository inactivity and wholly unpinned workflow actions add maintenance and build-hygiene risk.
No build attestation is present, so consumers have limited independent evidence connecting the artifact to its source. Staged publishing provides some process control but does not replace provenance.
The repository recorded zero commits and zero active maintainers in the last three months, a meaningful recent-maintenance concern despite the current registry release.
All 8 workflows were analyzed with no audit findings, and 7 use read-only permissions. However, all 12 action references are unpinned and one workflow has top-level write permissions; the pull_request_target triggers have no untrusted checkout or script-injection sink.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
es-errors Version ^1.3.0 | — | — |
path-parse Version ^1.0.7 | — | — |
is-core-module Version ^2.17.0 | — | — |
supports-preserve-symlinks-flag Version ^1.0.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.