babel-helper-replace-supers
Helper function to replace supers
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): amasad and thejameskyle are well-known Babel core contributors; this is a legitimate team expansion for the Babel monorepo, not a suspicious takeover. | ai | |
| phantom-deps | phantom-dep:babel-traverse | AI (phantom-deps): babel-traverse is a declared dependency in package.json and a core Babel package; phantom-dep detection is a false positive for this Babel helper's architecture. | ai | |
| dependencies | unvetted-dep:babel-traverse | AI (dependencies): babel-traverse is a core Babel package and a natural, expected dependency for any Babel helper that manipulates AST traversal. No risk. | ai | |
| phantom-deps | phantom-dep:babel-template | AI (phantom-deps): babel-template is explicitly declared in package.json dependencies; indirect usage pattern is normal for Babel helper packages. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by years; absence is expected and not a risk signal for this well-established Babel package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 6.24.1 | 6 / 0 | |
| 6.6.5 | 6 / 0 | |
| 6.2.0 | 6 / 0 | |
| 6.1.16 | 6 / 0 | |
| 6.1.13 | 6 / 0 | |
| 6.1.8 | 6 / 0 | |
| 6.1.7 | 6 / 0 | |
| 6.1.5 | 6 / 0 | |
| 6.0.15 | 6 / 0 | |
| 6.0.2 | 6 / 0 | |
| 6.0.0 | 6 / 0 |
v6.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.