Find the root directory of a Node.js project or npm package
18%
Total Score
50
70
50
npm marks the entire package as deprecated because it was renamed to package-directory. Package-scope deprecation is a severe adoption risk even though the release itself is not withdrawn.
The package has existed for more than 11 years with 12 releases, but it has had no releases in the last 15 months. The long history provides maturity, but the recent release gap adds maintenance concern.
The repository recorded zero commits and zero active maintainers in the last three months. This weakens evidence of ongoing maintenance, despite the repository not being archived.
The single workflow was fully analyzed with no reported audit findings or untrusted execution paths, but both of its two action references are unpinned, leaving avoidable build reproducibility risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
find-up-simple 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.