← Home

@types/minipass

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

6
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 @types redirect package; dormancy is expected — it only needs updating when upstream bundles its own types, a one-time event. Publisher has 10k+ approvals and 0 rejections. ai
publish-pattern new-deps-added AI (publish-pattern): Adding minipass as a runtime dep is the canonical stub @types pattern — it forwards type resolution to the upstream package. Not an attack vector here. ai
bogus-package bogus-package AI (bogus-package): Stub/redirect @types packages are intentionally tiny with no code, no README instructions, and no keywords. All signals are expected for this package type. ai
phantom-deps phantom-dep:minipass AI (phantom-deps): Stub package declares minipass as a dep for type resolution forwarding, not for direct import. Phantom-dep finding is a stable false positive for this package. ai

Versions (showing 6 of 6)

Version Deps Published
3.3.5 1 / 0
3.1.2 1 / 0
3.1.1 1 / 0
3.1.0 1 / 0
2.2.1 1 / 0
2.2.0 1 / 0

v3.3.5

1 finding
LOW No provenance attestation provenance

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

v3.1.2

1 finding
LOW No provenance attestation provenance

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

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v2.2.1

1 finding
LOW No provenance attestation provenance

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

v2.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.