@babel/plugin-syntax-throw-expressions
Allow parsing of Throw Expressions
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): nicolo-ribaudo is a well-known Babel core team member; the hzoo→nicolo-ribaudo transition is a documented legitimate maintainer handoff within the Babel project. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): nicolo-ribaudo is a trusted Babel core maintainer with a strong track record (5731 approved packages). Addition is part of a legitimate team transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of xtuc is part of the same legitimate Babel team maintainer transition; no evidence of compromise. | ai | |
| provenance | missing-githead | AI (provenance): Babel monorepo publish workflow change; no security implication. nicolo-ribaudo is a trusted core Babel maintainer and the package content is consistent with prior versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Babel monorepo produces many small, templated plugin packages by design. Tiny payload and mass-production signals are expected and benign for @babel/* packages. | ai | |
| provenance | no-provenance | AI (provenance): This version predates widespread Sigstore provenance adoption in the Babel publish pipeline; absence is expected for this era of releases. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 7.29.7 | 1 / 1 | |
| 7.28.6 | 1 / 1 | |
| 7.27.1 | 1 / 1 | |
| 7.25.9 | 1 / 1 | |
| 7.25.7 | 1 / 1 | |
| 7.24.7 | 1 / 1 | |
| 7.24.6 | 1 / 1 | |
| 7.24.1 | 1 / 1 | |
| 7.23.3 | 1 / 1 | |
| 7.22.5 | 1 / 1 | |
| 7.18.6 | 1 / 1 | |
| 7.16.7 | 1 / 1 | |
| 7.16.5 | 1 / 1 | |
| 7.16.0 | 1 / 1 | |
| 7.14.5 | 1 / 1 | |
| 7.12.13 | 1 / 1 | |
| 7.12.1 | 1 / 1 | |
| 7.10.4 | 1 / 1 | |
| 7.10.1 | 1 / 1 | |
| 7.8.3 | 1 / 1 | |
| 7.8.0 | 1 / 1 | |
| 7.7.4 | 1 / 1 | |
| 7.2.0 | 1 / 1 | |
| 7.0.0 | 1 / 1 |
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nicolo-ribaudo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nicolo-ribaudo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nicolo-ribaudo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nicolo-ribaudo.
v7.16.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nicolo-ribaudo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nicolo-ribaudo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nicolo-ribaudo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.13
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nicolo-ribaudo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nicolo-ribaudo.
[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
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
2 findingsThis version was published by a different npm account than previous versions on 2018-12-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.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.