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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Trusted metro-bot publisher; publish-env change on canonical Metro package, not a risk signal. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Metro monorepo packages use 0.0.0 placeholder versioning; established high-trust package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Minor metadata gap, not indicative of risk for this established package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Alias dep of existing @babel/traverse dependency already present; not a novel supply-chain risk. | 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 | |
| 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 | |
| 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 82 of 182)
| Version | Deps | Published |
|---|---|---|
| 0.59.0 | 7 / 2 | |
| 0.58.0 | 7 / 2 | |
| 0.57.0 | 7 / 2 | |
| 0.56.4 | 7 / 2 | |
| 0.56.3 | 7 / 2 | |
| 0.56.0 | 7 / 2 | |
| 0.55.0 | 7 / 2 | |
| 0.54.1 | 3 / 2 | |
| 0.54.0 | 3 / 2 | |
| 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 / 2 | |
| 0.45.0 | 1 / 2 | |
| 0.44.0 | 1 / 2 | |
| 0.43.6 | 1 / 2 | |
| 0.43.5 | 1 / 2 | |
| 0.43.4 | 1 / 2 | |
| 0.43.3 | 1 / 2 | |
| 0.43.2 | 1 / 2 | |
| 0.43.1 | 1 / 2 | |
| 0.43.0 | 1 / 2 | |
| 0.42.2 | 1 / 2 | |
| 0.42.1 | 1 / 2 | |
| 0.40.1 | 1 / 2 | |
| 0.40.0 | 1 / 2 | |
| 0.39.1 | 1 / 2 | |
| 0.39.0 | 1 / 2 | |
| 0.38.4 | 1 / 2 | |
| 0.38.3 | 1 / 2 | |
| 0.38.2 | 1 / 2 | |
| 0.38.1 | 1 / 2 | |
| 0.38.0 | 1 / 2 | |
| 0.37.2 | 1 / 2 | |
| 0.37.1 | 1 / 2 | |
| 0.37.0 | 1 / 2 | |
| 0.36.1 | 1 / 2 | |
| 0.36.0 | 1 / 2 | |
| 0.35.0 | 1 / 2 | |
| 0.34.0 | 1 / 2 | |
| 0.33.0 | 1 / 2 | |
| 0.32.0 | 1 / 2 | |
| 0.31.0 | 1 / 2 | |
| 0.30.2 | 1 / 2 | |
| 0.30.1 | 1 / 2 | |
| 0.30.0 | 1 / 2 | |
| 0.29.0 | 1 / 2 | |
| 0.28.0 | 1 / 2 | |
| 0.27.0 | 1 / 2 | |
| 0.26.0 | 1 / 2 | |
| 0.25.1 | 1 / 2 | |
| 0.25.0 | 1 / 2 | |
| 0.24.7 | 1 / 2 | |
| 0.24.6 | 1 / 2 | |
| 0.24.5 | 1 / 2 | |
| 0.24.4 | 1 / 2 | |
| 0.24.3 | 1 / 2 | |
| 0.24.2 | 1 / 2 | |
| 0.24.1 | 1 / 2 | |
| 0.24.0 | 1 / 2 | |
| 0.23.0 | 1 / 2 | |
| 0.0.0 | 0 / 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
2 findingsThis version was published by a different npm account (metro-bot) than the most recent previously approved version (rafeca) on 2018-11-29. It has since remained available on npm for 2790 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.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.
This version was published by a different npm account (rafeca) than the most recent previously approved version (metro-bot) on 2018-12-12, but rafeca is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rafeca) than the most recent previously approved version (kuvos) on 2017-12-20, but rafeca is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.