babel-plugin-transform-proto-to-assign MIT 17 versions

babel-plugin-transform-proto-to-assign

npm Repository

Babel plugin for turning __proto__ into a shallow property clone

17

Versions

MIT

License

No

Install Scripts

Missing

Provenance

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
bogus-package	bogus-package	AI (bogus-package): The flagged maintainers (hzoo, loganfsmyth, danez, sebmck, thejameskyle) are all well-known Babel core contributors, not spam actors. This is a false positive for this package.	ai	2026/04/23
provenance	publisher-changed	AI (provenance): Publisher change loganfsmyth→hzoo in 2017 reflects documented Babel team reorganization; hzoo is a known Babel core maintainer. Stable judgment for this package.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): danez is a known Babel core contributor; addition reflects legitimate team expansion, not a takeover.	ai	2026/04/23
maintainer-change	maintainer-removed	AI (maintainer-change): amasad and jmm removal is consistent with the 2017 Babel team reorganization; no evidence of malicious takeover.	ai	2026/04/23

Versions (showing 17 of 17)

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.9.0	2 / 1	2016-05-17
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.6.0	2 / 1	2016-02-29
6.5.0	2 / 1	2016-02-07
6.4.0	2 / 1	2016-01-06
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

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

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.

LOW No provenance attestation provenance

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

v6.23.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: hzoo → loganfsmyth (on 2017-02-13) provenance

[Accepted risk] 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.

v6.22.0

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v6.6.0

1 finding

LOW No provenance attestation provenance

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

v6.5.0

1 finding

LOW No provenance attestation provenance

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

v6.4.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: sebmck → hzoo (on 2016-01-06) provenance

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

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

LOW No provenance attestation provenance

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.