← Home

package-directory

npm Repository Homepage

Find the root directory of a Node.js project or npm package

10
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

sindresorhus

Keywords

packagejsonrootnpmentryfindupfind-upfinduplook-uplookfilesearchmatchresolveparentparentsfolderdirectorywalkwalkingpath

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-takeover AI (maintainer-change): Legitimate takeover by sindresorhus, one of npm's most trusted publishers (468 packages, 6492 approved versions). Consistent with their ecosystem maintenance pattern. ai
provenance publisher-changed AI (provenance): Publisher change from daluege to sindresorhus is a legitimate package adoption by a highly trusted maintainer. ai
maintainer-change maintainer-added AI (maintainer-change): sindresorhus added as maintainer during legitimate package adoption. ai
maintainer-change maintainer-removed AI (maintainer-change): Previous maintainer removed as part of legitimate transfer to sindresorhus. ai

Versions (showing 10 of 10)

Version Deps Published
8.2.0 1 / 4
8.1.0 1 / 4
0.2.3 1 / 0
0.2.2 1 / 0
0.2.1 1 / 0
0.2.0 1 / 0
0.1.6 1 / 0
0.1.5 1 / 0
0.1.4 1 / 0
0.1.3 1 / 0

v8.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.1.0

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (daluege) were replaced by new maintainers (sindresorhus). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: daluege → sindresorhus (on 2025-06-05) provenance

This version was published by a different npm account than previous versions on 2025-06-05. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.