← Home

@types/mkdirp

npm

Stub TypeScript definitions entry for mkdirp, which provides its own types definitions

9
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

types

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Stub/deprecation releases from @types packages naturally follow long dormancy periods when upstream bundles its own types. This pattern is expected for the types publisher. ai
publish-pattern new-deps-added AI (publish-pattern): Adding the upstream package as a runtime dep is the standard DefinitelyTyped stub pattern — ensures the real package with bundled types is installed. Not a supply-chain risk here. ai
bogus-package bogus-package AI (bogus-package): Stub deprecation shims legitimately have tiny payloads, no code blocks in README, and no keywords. All signals are false positives for this well-known @types stub pattern. ai
phantom-deps phantom-dep:mkdirp AI (phantom-deps): Stub package has no code to import from mkdirp; the dep is a redirect mechanism, not a code import. Phantom-dep finding is a false positive for this package type. ai

Versions (showing 9 of 9)

Version Deps Published
2.0.0 1 / 0
1.0.2 1 / 0
1.0.1 1 / 0
1.0.0 1 / 0
0.5.2 1 / 0
0.5.1 1 / 0
0.5.0 1 / 0
0.3.29 0 / 0
0.3.28 0 / 0

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
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. Consider requesting the maintainer enable provenance via CI/CD.

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.