← Home

mkdirp-then

npm Repository Homepage

mkdirp as promised

5
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

jongleberrystephenmathieson

Keywords

mkdirpthenthenablecofspromise

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from jongleberry to stephenmathieson occurred in 2015 — a decade-old settled transition, not a recent compromise. stephenmathieson has a strong track record. ai
maintainer-change maintainer-added AI (maintainer-change): Maintainer addition is the same 2015 transition; long-settled and publisher has strong approval history. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance attestation; absence is expected for this era of publishing. ai

Versions (showing 5 of 5)

Version Deps Published
1.2.0 2 / 4
1.1.1 2 / 4
1.1.0 2 / 4
1.0.1 2 / 4
1.0.0 2 / 3

v1.2.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.

v1.1.1

2 findings
HIGH Publisher changed: jongleberry → stephenmathieson (on 2015-12-31) provenance

This version was published by a different npm account than previous versions on 2015-12-31. 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.

v1.1.0

2 findings
HIGH Publisher changed: jongleberry → stephenmathieson (on 2015-07-10) provenance

This version was published by a different npm account than previous versions on 2015-07-10. 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.

v1.0.1

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.

v1.0.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.