← Home

pull-defer

npm Repository Homepage

a deferred source, sink or through pull-stream

7
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

dominictarr

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Package is 11+ years old from a highly trusted publisher; 0.0.0 versioning was a common pattern in the early npm/pull-stream ecosystem, not an indicator of malice. ai
phantom-deps phantom-dep:pull-stream AI (phantom-deps): pull-stream is a declared runtime dependency and core protocol dependency for this package; phantom-dep flag is a false positive for pull-stream ecosystem packages. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance by many years; absence of provenance is expected and not a risk signal for this established package. ai

Versions (showing 7 of 7)

Version Deps Published
0.2.3 0 / 4
0.2.2 0 / 4
0.2.1 1 / 1
0.2.0 1 / 1
0.1.1 1 / 0
0.1.0 1 / 0
0.0.0 1 / 0

v0.2.3

1 finding
LOW No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.1.0

1 finding
LOW No provenance attestation provenance

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

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