@babel/plugin-transform-classes
Compile ES2015 classes to ES5
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@babel/helper-annotate-as-pure | AI (dependencies): First-party Babel helper package from the same babel/babel monorepo; stable internal dependency with no security risk. | ai | |
| dependencies | unvetted-dep:@babel/helper-replace-supers | AI (dependencies): First-party Babel helper package from the same babel/babel monorepo; stable internal dependency with no security risk. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): nicolo-ribaudo is a documented Babel core maintainer; addition is a legitimate team roster change, not a takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): loganfsmyth and hzoo are well-known Babel contributors; spam flag is a false positive for high-volume legitimate Babel publishers. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of xtuc reflects routine Babel team changes; no hostile takeover indicators present. | ai | |
| provenance | publisher-changed | AI (provenance): nicolo-ribaudo is a well-known Babel core team member; the publisher change from hzoo is a legitimate team transition within the Babel project, stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Official Babel monorepo package published via GitHub Actions; lack of Sigstore provenance is common and not a risk signal for this well-established package. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 7.29.7 | 6 / 2 | |
| 7.28.6 | 6 / 2 | |
| 7.28.4 | 6 / 2 | |
| 7.28.3 | 6 / 2 | |
| 7.28.0 | 6 / 2 | |
| 7.27.7 | 6 / 2 | |
| 7.27.1 | 6 / 2 | |
| 7.25.9 | 6 / 2 | |
| 7.25.7 | 6 / 2 | |
| 7.25.4 | 6 / 2 | |
| 7.25.0 | 6 / 2 | |
| 7.24.8 | 8 / 3 | |
| 7.24.7 | 8 / 3 | |
| 7.24.6 | 8 / 3 | |
| 7.24.5 | 8 / 3 | |
| 7.24.1 | 8 / 3 | |
| 7.23.8 | 8 / 3 | |
| 7.23.5 | 9 / 3 | |
| 7.23.3 | 9 / 3 | |
| 7.22.15 | 9 / 3 | |
| 7.22.6 | 9 / 3 | |
| 7.22.5 | 9 / 3 | |
| 7.21.0 | 9 / 3 | |
| 7.20.7 | 9 / 3 | |
| 7.20.2 | 9 / 3 | |
| 7.19.0 | 9 / 3 | |
| 7.18.9 | 8 / 3 | |
| 7.18.8 | 8 / 3 | |
| 7.18.6 | 8 / 3 | |
| 7.18.4 | 8 / 3 | |
| 7.17.12 | 8 / 3 | |
| 7.16.7 | 8 / 3 | |
| 7.16.5 | 8 / 3 | |
| 7.16.0 | 7 / 3 | |
| 7.15.4 | 7 / 3 | |
| 7.14.9 | 7 / 3 | |
| 7.14.5 | 7 / 3 | |
| 7.14.4 | 7 / 3 | |
| 7.14.2 | 7 / 2 | |
| 7.13.0 | 7 / 2 | |
| 7.12.13 | 7 / 2 | |
| 7.12.1 | 8 / 2 | |
| 7.10.4 | 8 / 2 | |
| 7.10.3 | 8 / 2 | |
| 7.10.1 | 8 / 2 | |
| 7.9.5 | 8 / 2 | |
| 7.9.2 | 8 / 2 | |
| 7.9.0 | 8 / 2 | |
| 7.8.6 | 8 / 2 | |
| 7.8.3 | 8 / 2 | |
| 7.8.0 | 8 / 2 |
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.4
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.28.3
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.28.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.
v7.27.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.27.1
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.4
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.25.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.
v7.24.8
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.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.5
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.23.8
2 findingsThis version was published by a different npm account than previous versions on 2024-01-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.23.5
2 findingsThis version was published by a different npm account than previous versions on 2023-11-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.23.3
2 findingsThis version was published by a different npm account than previous versions on 2023-11-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.22.15
2 findingsThis version was published by a different npm account than previous versions on 2023-09-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.22.6
2 findingsThis version was published by a different npm account than previous versions on 2023-07-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.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.21.0
2 findingsThis version was published by a different npm account than previous versions on 2023-02-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.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.20.2
2 findingsThis version was published by a different npm account than previous versions on 2022-11-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.19.0
2 findingsThis version was published by a different npm account than previous versions on 2022-09-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.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.8
2 findingsThis version was published by a different npm account than previous versions on 2022-07-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.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.4
2 findingsThis version was published by a different npm account than previous versions on 2022-05-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.17.12
2 findingsThis version was published by a different npm account than previous versions on 2022-05-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.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.14.9
2 findingsThis version was published by a different npm account than previous versions on 2021-08-01. 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.2
2 findingsThis version was published by a different npm account than previous versions on 2021-05-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.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.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.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.3
2 findingsThis version was published by a different npm account than previous versions on 2020-06-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.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.9.5
2 findingsThis version was published by a different npm account than previous versions on 2020-04-07. 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.2
2 findingsThis version was published by a different npm account than previous versions on 2020-03-21. 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.0
2 findingsThis version was published by a different npm account than previous versions on 2020-03-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.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.