← Home

rollup-plugin-alias

npm Repository Homepage
16
Versions
—
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

lukastaegertrich_harrisstoney

Keywords

rolluprollup-pluginresolvealias

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): rich_harris (Rich Harris, Rollup creator) taking over a rollup ecosystem plugin is a legitimate and well-documented maintainer transition. No malicious signals accompany the change. ai
maintainer-change maintainer-added AI (maintainer-change): Addition of rich_harris as maintainer is consistent with legitimate ecosystem stewardship of a rollup plugin by Rollup's own creator. ai

Versions (showing 16 of 16)

Version Deps Published
2.2.0 1 / 8
2.1.0 1 / 8
2.0.1 1 / 8
2.0.0 1 / 8
1.5.2 1 / 8
1.5.1 1 / 8
1.5.0 1 / 8
1.4.0 1 / 8
1.3.1 1 / 10
1.3.0 0 / 11
1.2.1 0 / 10
1.2.0 0 / 10
1.1.0 0 / 10
1.0.2 0 / 10
1.0.1 0 / 10
1.0.0 0 / 10

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

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

v1.5.2

2 findings
HIGH Publisher changed: stoney → lukastaegert (on 2019-06-01) provenance

This version was published by a different npm account than previous versions on 2019-06-01. 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.

v1.5.1

2 findings
HIGH Publisher changed: stoney → lukastaegert (on 2018-12-11) provenance

This version was published by a different npm account than previous versions on 2018-12-11. 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.

v1.5.0

2 findings
HIGH Publisher changed: stoney → lukastaegert (on 2018-12-11) provenance

This version was published by a different npm account than previous versions on 2018-12-11. 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.

v1.4.0

2 findings
HIGH Publisher changed: stoney → rich_harris (on 2017-10-19) provenance

This version was published by a different npm account than previous versions on 2017-10-19. 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.

v1.3.1

1 finding
LOW No provenance attestation provenance

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

v1.3.0

2 findings
HIGH Publisher changed: stoney → rich_harris (on 2017-04-10) provenance

This version was published by a different npm account than previous versions on 2017-04-10. 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.

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. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

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