← Home

@rollup/plugin-virtual

Load virtual modules from memory

8
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

shellscaperich_harrisguybedfordlukastaegert

Keywords

rolluppluginmemorymodulemodulesvirtual

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): lukastaegert is the primary Rollup maintainer; transition from shellscape to lukastaegert is a documented, legitimate handoff within the official rollup/plugins monorepo. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy reflects a stable, feature-complete plugin; activity resumed due to legitimate maintainer transition, not account takeover. ai

Versions (showing 8 of 8)

Version Deps Published
3.0.2 0 / 4
3.0.1 0 / 4
3.0.0 0 / 4
2.1.0 0 / 4
2.0.3 0 / 2
2.0.2 0 / 2
2.0.1 0 / 2
2.0.0 0 / 2

v3.0.2

2 findings
HIGH Publisher changed: shellscape → lukastaegert (on 2023-10-05) provenance

This version was published by a different npm account than previous versions on 2023-10-05. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

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.

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

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

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