metro-source-map
🚇 Source map generator for Metro.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@babel/traverse--for-generate-function-map | AI (dependencies): npm alias for @babel/traverse; same vetted package under a different local name, stable pattern in metro monorepo. | ai | |
| phantom-deps | phantom-dep:@babel/traverse | AI (phantom-deps): Loaded via the alias @babel/traverse--for-generate-function-map; phantom-dep false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Meta/Facebook migrated metro releases to GitHub Actions CI; SLSA attestation confirms legitimate CI/CD provenance. | ai | |
| bogus-package | bogus-package | AI (bogus-package): metro-source-map is a monorepo sub-package; short README and no keywords are expected for internal ecosystem packages published from facebook/metro. | ai | |
| phantom-deps | phantom-dep:flow-enums-runtime | AI (phantom-deps): flow-enums-runtime is a Flow type runtime used in the metro ecosystem; phantom-dep finding is expected for monorepo packages with shared type dependencies. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.84.4 | 9 / 3 | |
| 0.84.3 | 9 / 3 | |
| 0.84.2 | 9 / 3 | |
| 0.84.1 | 9 / 3 | |
| 0.84.0 | 9 / 3 | |
| 0.83.7 | 9 / 3 | |
| 0.83.6 | 9 / 3 | |
| 0.83.5 | 9 / 3 | |
| 0.83.4 | 9 / 3 | |
| 0.83.3 | 10 / 3 | |
| 0.83.2 | 10 / 3 | |
| 0.82.2 | 10 / 3 | |
| 0.81.5 | 10 / 3 |
v0.84.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.84.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.84.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.84.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.5
2 findingsThis version was published by a different npm account than previous versions on 2026-03-01. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.83.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.83.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.82.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.81.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.