contains-path
Return true if a file path contains the given path.
2
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
jonschlinkert
Keywords
containsdirectorydirnameexecextextnamefilefilepathfphasmatchmatchespathregextest
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): jonschlinkert maintains a large portfolio; sporadic updates to small utility packages are normal. No account takeover indicators present. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): normalize-path and path-starts-with are both jonschlinkert's own well-known packages, appropriate for a path utility. Not analogous to supply-chain injection. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from 658B to 2KB is consistent with delegating logic to two new utility deps. Total size remains tiny with no obfuscation. | ai |
v1.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.