Check if a path is in the current working directory
68%
Total Score
50
100
88
83
50
No build attestation or trusted-publisher provenance is present, leaving publication origin less independently verifiable. This is a transparency gap, but not severe enough to outweigh the otherwise clear package metadata.
The repository is owned by an individual rather than an organization, so there is no organizational maintenance buffer. The matching repository and named maintainer provide some direct ownership evidence.
The package has existed for over 12 years and has 8 releases, but its latest release was over five years ago and it had no releases in the last 12 months. This is a meaningful maintenance concern despite the package's mature history.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the release gap. That weakens evidence of ongoing maintenance, though it does not show that the package is abandoned.
The repository reports no build tool or security scanning tool. For this small package that is a modest hygiene gap, though the source remains simple and inspectable.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
is-path-inside Version ^4.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.