babel-plugin-transform-object-rest-spread

Compile object rest and spread to ES5

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

thejameskylesebmckdanezhzoologanfsmyth

Keywords

babel-plugin

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 Babel core team (hzoo → loganfsmyth); both are well-known Babel maintainers.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Published in 2017, before Sigstore provenance existed. Expected for legacy Babel packages.	ai	2026/04/24

Versions (showing 18 of 18)

Version	Deps	Published
6.26.0	2 / 1	2017-08-16
6.23.0	2 / 1	2017-02-13
6.22.0	2 / 1	2017-01-20
6.20.2	2 / 1	2016-12-09
6.20.1	2 / 1	2016-12-09
6.20.0	2 / 1	2016-12-08
6.19.0	2 / 1	2016-11-16
6.16.0	2 / 1	2016-09-28
6.8.0	2 / 1	2016-05-02
6.6.5	2 / 1	2016-03-04
6.6.4	2 / 1	2016-03-02
6.3.13	2 / 1	2015-12-04
6.2.4	2 / 1	2015-11-25
6.1.18	2 / 1	2015-11-12
6.1.17	2 / 1	2015-11-12
6.1.4	2 / 1	2015-11-11
6.0.14	2 / 0	2015-10-30
6.0.2	2 / 0	2015-10-29

v6.26.0

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: loganfsmyth → hzoo (on 2017-08-16) provenance

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

v6.23.0

2 findings

HIGH Publisher changed: hzoo → loganfsmyth (on 2017-02-13) provenance

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

v6.22.0

1 finding

INFO No provenance attestation provenance

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

v6.20.2

1 finding

INFO No provenance attestation provenance

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

v6.20.1

1 finding

INFO No provenance attestation provenance

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

v6.20.0

1 finding

INFO No provenance attestation provenance

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

v6.19.0

1 finding

LOW No provenance attestation provenance

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

v6.16.0

1 finding

LOW No provenance attestation provenance

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

v6.8.0

1 finding

LOW No provenance attestation provenance

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

v6.6.5

1 finding

LOW No provenance attestation provenance

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

v6.6.4

2 findings

HIGH Publisher changed: sebmck → hzoo (on 2016-03-02) provenance

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

v6.3.13

1 finding

LOW No provenance attestation provenance

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

v6.2.4

1 finding

INFO No provenance attestation provenance

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

v6.1.18

1 finding

LOW No provenance attestation provenance

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

v6.1.17

1 finding

LOW No provenance attestation provenance

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

v6.1.4

1 finding

LOW No provenance attestation provenance

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

v6.0.14

1 finding

LOW No provenance attestation provenance

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

v6.0.2

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.