metro-babel7-plugin-react-transform
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from rafeca to metro-bot occurred in 2018 and reflects Meta's transition to a bot publisher for Metro packages. Stable across 56 versions with 119 approved packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Metro ecosystem internal tooling package; missing metadata (description, repo, keywords) is consistent with Meta's monorepo publishing style, not a spam/malware indicator. | ai |
Versions (showing 56 of 56)
| Version | Deps | Published |
|---|---|---|
| 0.54.1 | 1 / 0 | |
| 0.54.0 | 1 / 0 | |
| 0.53.1 | 1 / 0 | |
| 0.53.0 | 1 / 0 | |
| 0.52.0 | 1 / 0 | |
| 0.51.1 | 1 / 0 | |
| 0.51.0 | 1 / 0 | |
| 0.50.0 | 1 / 0 | |
| 0.49.2 | 1 / 0 | |
| 0.49.1 | 1 / 0 | |
| 0.49.0 | 1 / 0 | |
| 0.48.5 | 1 / 0 | |
| 0.48.4 | 1 / 0 | |
| 0.48.3 | 1 / 0 | |
| 0.48.2 | 1 / 0 | |
| 0.48.1 | 1 / 0 | |
| 0.48.0 | 1 / 0 | |
| 0.47.1 | 1 / 0 | |
| 0.47.0 | 1 / 0 | |
| 0.46.0 | 1 / 0 | |
| 0.45.6 | 1 / 0 | |
| 0.45.5 | 1 / 0 | |
| 0.45.4 | 1 / 0 | |
| 0.45.3 | 1 / 0 | |
| 0.45.2 | 1 / 0 | |
| 0.45.1 | 1 / 0 | |
| 0.45.0 | 1 / 0 | |
| 0.44.0 | 1 / 0 | |
| 0.43.6 | 1 / 0 | |
| 0.43.5 | 1 / 0 | |
| 0.43.4 | 1 / 0 | |
| 0.43.3 | 1 / 0 | |
| 0.43.2 | 1 / 0 | |
| 0.43.1 | 1 / 0 | |
| 0.43.0 | 1 / 0 | |
| 0.42.2 | 1 / 0 | |
| 0.42.1 | 1 / 0 | |
| 0.40.1 | 1 / 0 | |
| 0.40.0 | 2 / 0 | |
| 0.39.1 | 2 / 0 | |
| 0.39.0 | 2 / 0 | |
| 0.38.4 | 2 / 0 | |
| 0.38.3 | 2 / 0 | |
| 0.38.2 | 2 / 0 | |
| 0.38.1 | 2 / 0 | |
| 0.38.0 | 2 / 0 | |
| 0.37.2 | 2 / 0 | |
| 0.37.1 | 2 / 0 | |
| 0.37.0 | 2 / 0 | |
| 0.36.1 | 2 / 0 | |
| 0.36.0 | 2 / 0 | |
| 0.35.0 | 2 / 0 | |
| 0.34.0 | 2 / 0 | |
| 0.33.0 | 2 / 0 | |
| 0.32.0 | 2 / 0 | |
| 0.30.3 | 2 / 0 |
v0.54.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
2 findingsPackage 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 2018-12-18. This could indicate a legitimate maintainer transition or an account compromise.
v0.50.0
2 findingsThis version was published by a different npm account than previous versions on 2018-11-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.4
2 findingsPackage 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 2018-12-12. This could indicate a legitimate maintainer transition or an account compromise.
v0.48.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.