← Home

@jspm/plugin-rollup

npm Repository Homepage

Rollup plugin for jspm 2

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

guybedfordjkrishnabubblyworld

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file:transform-cjs-dew.cjs AI (source-diff): transform-cjs-dew.cjs is a Babel AST-based CJS-to-ESM transform plugin; dynamic code generation is its core function, not malware. No actual network calls present in the file. ai
phantom-deps phantom-dep:@jspm/core AI (phantom-deps): @jspm/core is in the same org scope and is a legitimate declared dependency used indirectly by this JSPM plugin. ai

Versions (showing 6 of 6)

Version Deps Published
3.0.0 8 / 5
1.2.4 8 / 5
1.2.3 8 / 5
1.2.2 8 / 5
1.2.1 8 / 5
1.2.0 8 / 5

v3.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.2.4

2 findings
HIGH New file with network + code execution: transform-cjs-dew.cjs source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v1.2.3

1 finding
LOW No provenance attestation provenance

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

v1.2.2

1 finding
LOW No provenance attestation provenance

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

v1.2.1

1 finding
LOW No provenance attestation provenance

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

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