rollup-plugin-buble MIT 26 versions

rollup-plugin-buble

npm Repository Homepage

Compile ES2015 with buble

26

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

adrianheinelukastaegertrich_harris

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate maintainer transition within the rollup ecosystem; adrianheine is a known rollup contributor with a strong track record. Not an account compromise.	ai	2026/04/23
publish-pattern	dormant-publish	AI (publish-pattern): Dormancy is consistent with the maintainer transition in 2019; no other suspicious signals present.	ai	2026/04/23

Versions (showing 26 of 26)

Version	Deps	Published
0.19.8	2 / 3	2019-07-03
0.19.6	2 / 3	2018-12-09
0.19.4	2 / 3	2018-10-08
0.19.2	2 / 3	2018-02-13
0.19.1	2 / 3	2018-02-10
0.19.0	2 / 3	2018-02-09
0.18.0	2 / 3	2017-11-18
0.17.0	2 / 3	2017-11-05
0.16.0	2 / 3	2017-09-23
0.15.0	2 / 3	2016-12-13
0.14.0	2 / 3	2016-09-18
0.13.0	2 / 3	2016-08-15
0.12.1	2 / 3	2016-06-23
0.12.0	2 / 3	2016-06-22
0.11.0	2 / 3	2016-06-14
0.10.0	2 / 3	2016-05-25
0.9.0	2 / 3	2016-05-21
0.8.0	2 / 3	2016-05-15
0.7.0	2 / 3	2016-05-04
0.6.0	2 / 3	2016-04-24
0.5.0	2 / 3	2016-04-17
0.4.0	2 / 3	2016-04-08
0.3.4	2 / 3	2016-04-08
0.2.3	2 / 3	2016-04-08
0.2.2	2 / 3	2016-04-08
0.1.0	2 / 3	2016-04-07

v0.19.8

2 findings

HIGH Publisher changed: lukastaegert → adrianheine (on 2019-07-03) provenance

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

v0.19.6

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: adrianheine → lukastaegert (on 2018-12-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-12-09. This could indicate a legitimate maintainer transition or an account compromise.

v0.19.4

1 finding

LOW No provenance attestation provenance

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

v0.19.2

1 finding

LOW No provenance attestation provenance

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

v0.19.1

1 finding

LOW No provenance attestation provenance

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

v0.19.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: rich_harris → adrianheine (on 2018-02-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-02-09. This could indicate a legitimate maintainer transition or an account compromise.

v0.18.0

1 finding

LOW No provenance attestation provenance

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

v0.17.0

1 finding

LOW No provenance attestation provenance

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

v0.16.0

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.0

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

v0.12.1

1 finding

LOW No provenance attestation provenance

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

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.2.3

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

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