@babel/plugin-transform-typescript
Transform TypeScript into ES.next
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @babel/helper-create-class-features-plugin is a first-party Babel scoped package; adding it is a legitimate and expected dependency for this TypeScript transform plugin. | ai | |
| provenance | publisher-changed | AI (provenance): Babel migrated to GitHub Actions for automated publishing; this is the expected publisher for all new versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): nicolo-ribaudo and jlhwung are established Babel core team members; legitimate maintainer evolution. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers are former Babel team members; natural team turnover over many years. | ai | |
| bogus-package | bogus-package | AI (bogus-package): hzoo (Henry Zhu) is the Babel project founder; spam flag is a false positive. | ai | |
| provenance | no-provenance | AI (provenance): Official Babel monorepo package published via GitHub Actions CI; lack of Sigstore provenance is acceptable for this well-known package. | ai |
Versions (showing 51 of 98)
| Version | Deps | Published |
|---|---|---|
| 7.29.7 | 5 / 4 | |
| 7.28.6 | 5 / 4 | |
| 7.28.5 | 5 / 4 | |
| 7.28.0 | 5 / 4 | |
| 7.27.1 | 5 / 4 | |
| 7.27.0 | 5 / 4 | |
| 7.26.8 | 5 / 4 | |
| 7.26.7 | 5 / 4 | |
| 7.26.5 | 5 / 4 | |
| 7.26.3 | 5 / 4 | |
| 7.25.9 | 5 / 4 | |
| 7.25.7 | 5 / 4 | |
| 7.25.2 | 5 / 4 | |
| 7.25.0 | 5 / 4 | |
| 7.24.8 | 4 / 4 | |
| 7.24.7 | 4 / 4 | |
| 7.24.6 | 4 / 4 | |
| 7.24.5 | 4 / 4 | |
| 7.24.4 | 4 / 4 | |
| 7.24.1 | 4 / 4 | |
| 7.23.6 | 4 / 4 | |
| 7.23.5 | 4 / 4 | |
| 7.23.4 | 4 / 4 | |
| 7.23.3 | 4 / 4 | |
| 7.22.15 | 4 / 4 | |
| 7.22.11 | 4 / 4 | |
| 7.22.10 | 4 / 4 | |
| 7.22.9 | 4 / 4 | |
| 7.22.5 | 4 / 4 | |
| 7.22.3 | 4 / 4 | |
| 7.22.0 | 4 / 4 | |
| 7.21.3 | 4 / 4 | |
| 7.21.0 | 3 / 4 | |
| 7.20.13 | 3 / 4 | |
| 7.20.7 | 3 / 4 | |
| 7.20.2 | 3 / 4 | |
| 7.20.0 | 3 / 4 | |
| 7.19.3 | 3 / 4 | |
| 7.19.1 | 3 / 4 | |
| 7.19.0 | 3 / 4 | |
| 7.18.12 | 3 / 4 | |
| 7.18.10 | 3 / 4 | |
| 7.18.8 | 3 / 4 | |
| 7.18.6 | 3 / 4 | |
| 7.18.4 | 3 / 4 | |
| 7.18.1 | 3 / 4 | |
| 7.18.0 | 3 / 4 | |
| 7.17.12 | 3 / 4 | |
| 7.16.8 | 3 / 4 | |
| 7.16.7 | 3 / 4 | |
| 7.16.1 | 3 / 4 |
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
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.28.5
2 findingsThis version was published by a different npm account than previous versions on 2025-10-23. 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.28.0
2 findingsThis version was published by a different npm account than previous versions on 2025-07-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.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.27.0
2 findingsThis version was published by a different npm account than previous versions on 2025-03-24. 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.8
2 findingsThis version was published by a different npm account than previous versions on 2025-02-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.26.7
2 findingsThis version was published by a different npm account than previous versions on 2025-01-24. 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
2 findingsThis version was published by a different npm account than previous versions on 2025-01-10. 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.3
2 findingsThis version was published by a different npm account than previous versions on 2024-12-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.25.9
2 findingsThis version was published by a different npm account than previous versions on 2024-10-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.25.7
2 findingsThis version was published by a different npm account than previous versions on 2024-10-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.25.2
2 findingsThis version was published by a different npm account than previous versions on 2024-07-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.25.0
2 findingsThis version was published by a different npm account than previous versions on 2024-07-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.24.8
2 findingsThis version was published by a different npm account than previous versions on 2024-07-11. 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.24.7
2 findingsThis version was published by a different npm account than previous versions on 2024-06-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.24.6
2 findingsThis version was published by a different npm account than previous versions on 2024-05-24. 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.24.5
2 findingsThis version was published by a different npm account than previous versions on 2024-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.24.4
2 findingsThis version was published by a different npm account than previous versions on 2024-04-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.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.6
2 findingsThis version was published by a different npm account than previous versions on 2023-12-11. 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.4
2 findingsThis version was published by a different npm account than previous versions on 2023-11-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.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.11
2 findingsThis version was published by a different npm account than previous versions on 2023-08-24. 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.10
2 findingsThis version was published by a different npm account than previous versions on 2023-08-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.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.3
2 findingsThis version was published by a different npm account than previous versions on 2023-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.22.0
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.3
2 findingsThis version was published by a different npm account than previous versions on 2023-03-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.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.13
2 findingsThis version was published by a different npm account than previous versions on 2023-01-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.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.20.0
2 findingsThis version was published by a different npm account than previous versions on 2022-10-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.19.3
2 findingsThis version was published by a different npm account than previous versions on 2022-09-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.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.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.12
2 findingsThis version was published by a different npm account than previous versions on 2022-08-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.10
2 findingsThis version was published by a different npm account than previous versions on 2022-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.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.18.1
2 findingsThis version was published by a different npm account than previous versions on 2022-05-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.18.0
2 findingsThis version was published by a different npm account than previous versions on 2022-05-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.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.8
2 findingsThis version was published by a different npm account than previous versions on 2022-01-10. 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.1
2 findingsThis version was published by a different npm account than previous versions on 2021-10-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.