← Home

@lumenize/fetch

npm

De✨light✨ful fetch utilities for Durable Objects - proxy and direct fetch strategies

6
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

lmaccherone

Keywords

cloudflareworkersdurable-objectsfetchqueuecost-optimizationdx

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established publisher; low-risk package with no install scripts or obfuscation. ai
phantom-deps phantom-dep:@lumenize/routing AI (phantom-deps): Same-org monorepo package; declared as runtime dep, likely used transitively within the @lumenize scope. ai
phantom-deps phantom-dep:@lumenize/test-endpoints AI (phantom-deps): Same-org test utility; declared dep used indirectly in test infrastructure, stable false positive for this package. ai

Versions (showing 6 of 6)

Version Deps Published
0.26.0 4 / 7
0.25.0 5 / 6
0.24.0 5 / 5
0.23.0 5 / 5
0.22.0 5 / 5
0.20.0 5 / 5

v0.26.0

1 finding
INFO No provenance attestation provenance

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

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

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

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

v0.22.0

1 finding
LOW No provenance attestation provenance

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

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