metro-babel-transformer
🚇 Base Babel transformer for Metro.
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-stale | AI (provenance): Old, stable publisher change; cpojer is a long-standing trusted metro maintainer. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same metro-bot transition pattern across metro packages. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): metro-bot is Facebook's established automation publisher for the metro monorepo, not a hijack. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Individual maintainer replaced by org automation account, consistent with monorepo migration. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): metro-source-map is a first-party sibling package in the same monorepo. | ai | |
| phantom-deps | phantom-dep:flow-enums-runtime | AI (phantom-deps): flow-enums-runtime is a runtime dep used by Flow-typed code at runtime, not directly imported in JS; stable false positive for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects upstream release cadence for facebook/metro, not account takeover; SLSA attestation confirms integrity. | ai | |
| provenance | publisher-changed | AI (provenance): Meta/facebook migrated metro packages to GitHub Actions CI publishing; SLSA attestation confirms legitimate CI origin. | ai |
Versions (showing 15 of 115)
| Version | Deps | Published |
|---|---|---|
| 0.59.0 | 2 / 0 | |
| 0.58.0 | 2 / 0 | |
| 0.57.0 | 2 / 0 | |
| 0.56.4 | 2 / 0 | |
| 0.56.3 | 2 / 0 | |
| 0.56.0 | 2 / 0 | |
| 0.55.0 | 2 / 0 | |
| 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 |
v0.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
2 findingsThis version was published by a different npm account (metro-bot) than the most recent previously approved version (rafeca) on 2018-12-21. It has since remained available on npm for 2768 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.