@babel/helper-replace-supers
Helper function to replace supers
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): nicolo-ribaudo is a core Babel maintainer; the hzoo→nicolo-ribaudo transition is a known legitimate Babel team change, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): nicolo-ribaudo and jlhwung are known Babel team members; additions reflect legitimate team restructuring. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers are former Babel contributors; removal is part of known Babel team restructuring, not a takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): hzoo is Henry Zhu (Babel project lead), not a spam publisher. No-keywords is irrelevant for a core Babel helper. Both signals are false positives for this package. | ai | |
| provenance | no-provenance | AI (provenance): Babel publishes via GitHub Actions CI without Sigstore provenance; this is consistent across the entire Babel monorepo release pipeline and not a security concern. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 7.29.7 | 3 / 1 | |
| 7.28.6 | 3 / 1 | |
| 7.27.1 | 3 / 1 | |
| 7.26.5 | 3 / 1 | |
| 7.25.9 | 3 / 1 | |
| 7.25.7 | 3 / 1 | |
| 7.25.0 | 3 / 1 | |
| 7.24.7 | 3 / 1 | |
| 7.24.6 | 3 / 1 | |
| 7.24.1 | 3 / 1 | |
| 7.22.20 | 3 / 1 | |
| 7.22.9 | 3 / 1 | |
| 7.22.5 | 6 / 0 | |
| 7.22.1 | 6 / 0 | |
| 7.21.5 | 6 / 0 | |
| 7.20.7 | 6 / 0 | |
| 7.19.1 | 5 / 0 | |
| 7.18.9 | 5 / 0 | |
| 7.18.6 | 5 / 0 | |
| 7.18.2 | 5 / 0 | |
| 7.16.7 | 5 / 0 | |
| 7.16.5 | 5 / 0 | |
| 7.16.0 | 4 / 0 | |
| 7.15.4 | 4 / 0 | |
| 7.15.0 | 4 / 0 | |
| 7.14.5 | 4 / 0 | |
| 7.14.4 | 4 / 0 | |
| 7.14.3 | 4 / 0 | |
| 7.13.12 | 4 / 0 | |
| 7.13.0 | 4 / 0 | |
| 7.12.13 | 4 / 0 | |
| 7.12.11 | 4 / 0 | |
| 7.12.5 | 4 / 0 | |
| 7.12.1 | 4 / 0 | |
| 7.12.0 | 4 / 0 | |
| 7.10.4 | 4 / 0 | |
| 7.10.1 | 4 / 0 | |
| 7.10.0 | 4 / 0 | |
| 7.9.6 | 4 / 0 | |
| 7.8.6 | 4 / 0 | |
| 7.8.3 | 4 / 0 | |
| 7.8.0 | 4 / 0 | |
| 7.7.4 | 4 / 0 | |
| 7.7.0 | 4 / 0 | |
| 7.5.5 | 4 / 0 | |
| 7.4.4 | 4 / 0 | |
| 7.4.0 | 4 / 0 | |
| 7.3.4 | 4 / 0 | |
| 7.2.3 | 4 / 0 | |
| 7.1.0 | 4 / 0 | |
| 7.0.0 | 4 / 0 |
v7.29.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.28.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-01-12. This could indicate a legitimate maintainer transition or an account compromise.
v7.27.1
2 findingsThis version was published by a different npm account than previous versions on 2025-04-30. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.24.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.24.1
2 findingsThis version was published by a different npm account than previous versions on 2024-03-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.20
2 findingsThis version was published by a different npm account than previous versions on 2023-09-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.9
2 findingsThis version was published by a different npm account than previous versions on 2023-07-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.5
2 findingsThis version was published by a different npm account than previous versions on 2023-06-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.1
2 findingsThis version was published by a different npm account than previous versions on 2023-05-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.21.5
2 findingsThis version was published by a different npm account than previous versions on 2023-04-28. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.7
2 findingsThis version was published by a different npm account than previous versions on 2022-12-22. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.1
2 findingsThis version was published by a different npm account than previous versions on 2022-09-14. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.9
2 findingsThis version was published by a different npm account than previous versions on 2022-07-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.6
2 findingsThis version was published by a different npm account than previous versions on 2022-06-27. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.2
2 findingsThis version was published by a different npm account than previous versions on 2022-05-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.7
2 findingsThis version was published by a different npm account than previous versions on 2021-12-31. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.5
2 findingsThis version was published by a different npm account than previous versions on 2021-12-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.0
2 findingsThis version was published by a different npm account than previous versions on 2021-10-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.4
2 findingsThis version was published by a different npm account than previous versions on 2021-09-02. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.0
2 findingsThis version was published by a different npm account than previous versions on 2021-08-04. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.5
2 findingsThis version was published by a different npm account than previous versions on 2021-06-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.4
2 findingsThis version was published by a different npm account than previous versions on 2021-05-28. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.3
2 findingsThis version was published by a different npm account than previous versions on 2021-05-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.12
2 findingsThis version was published by a different npm account than previous versions on 2021-03-22. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.0
2 findingsThis version was published by a different npm account than previous versions on 2021-02-22. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.13
2 findingsThis version was published by a different npm account than previous versions on 2021-02-03. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.11
2 findingsThis version was published by a different npm account than previous versions on 2020-12-15. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.5
2 findingsThis version was published by a different npm account than previous versions on 2020-11-03. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.1
2 findingsThis version was published by a different npm account than previous versions on 2020-10-15. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.0
2 findingsThis version was published by a different npm account than previous versions on 2020-10-14. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.4
2 findingsThis version was published by a different npm account than previous versions on 2020-06-30. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.1
2 findingsThis version was published by a different npm account than previous versions on 2020-05-27. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.0
2 findingsThis version was published by a different npm account than previous versions on 2020-05-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.6
2 findingsThis version was published by a different npm account than previous versions on 2020-04-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.6
2 findingsThis version was published by a different npm account than previous versions on 2020-02-27. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.3
2 findingsThis version was published by a different npm account than previous versions on 2020-01-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
2 findingsThis version was published by a different npm account than previous versions on 2020-01-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.4
2 findingsThis version was published by a different npm account than previous versions on 2019-11-22. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
2 findingsThis version was published by a different npm account than previous versions on 2019-11-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.5
2 findingsThis version was published by a different npm account than previous versions on 2019-07-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.4
2 findingsThis version was published by a different npm account than previous versions on 2019-04-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
2 findingsThis version was published by a different npm account than previous versions on 2019-03-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.4
2 findingsThis version was published by a different npm account than previous versions on 2019-02-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.3
2 findingsThis version was published by a different npm account than previous versions on 2018-12-20. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.