← Home

@jsenv/plugin-bundling

npm Repository Homepage
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

jsenv-admindmail

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata no-description AI (npm-metadata): Intentional omission in jsenv monorepo packages; stable pattern across versions. ai
provenance no-provenance AI (provenance): No provenance across jsenv packages; consistent pattern, not a risk indicator here. ai
dependencies unvetted-dep:@jsenv/urls AI (dependencies): First-party jsenv monorepo dependency; stable pattern across all versions of this package. ai
dependencies unvetted-dep:@jsenv/url-meta AI (dependencies): First-party jsenv monorepo dependency; stable pattern across all versions of this package. ai
dependencies unvetted-dep:@jsenv/sourcemap AI (dependencies): First-party jsenv monorepo dependency; stable pattern across all versions of this package. ai

Versions (showing 7 of 7)

Version Deps Published
2.10.11 7 / 2
2.10.10 7 / 2
2.10.8 7 / 2
2.10.7 7 / 2
2.10.4 7 / 2
2.10.1 7 / 2
2.9.12 7 / 1

v2.10.11

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.

v2.10.10

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.

v2.10.8

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.

v2.10.7

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.

v2.10.4

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.

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

v2.9.12

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.