mkdirp2
Recursively mkdir, like `mkdir -p`
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:mkdirp | AI (typosquat): Legitimate long-lived package (9+ years, 172k downloads) by trusted publisher 75lb; not a typosquat despite name similarity to mkdirp. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.0.5 | 0 / 2 | |
| 1.0.4 | 0 / 2 | |
| 1.0.3 | 0 / 2 | |
| 1.0.2 | 0 / 2 | |
| 1.0.1 | 0 / 2 | |
| 1.0.0 | 0 / 2 |
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsPackage name 'mkdirp2' is 1 edit(s) away from popular package 'mkdirp'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findingsPackage name 'mkdirp2' is 1 edit(s) away from popular package 'mkdirp'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.