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 51 of 182)
| Version | Deps | Published |
|---|---|---|
| 0.87.0 | 9 / 3 | |
| 0.86.0 | 9 / 3 | |
| 0.85.0 | 9 / 3 | |
| 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.83.1 | 10 / 3 | |
| 0.83.0 | 10 / 3 | |
| 0.82.5 | 10 / 3 | |
| 0.82.4 | 10 / 3 | |
| 0.82.3 | 10 / 3 | |
| 0.82.2 | 10 / 3 | |
| 0.82.1 | 10 / 3 | |
| 0.82.0 | 10 / 3 | |
| 0.81.5 | 10 / 3 | |
| 0.81.4 | 10 / 3 | |
| 0.81.3 | 10 / 3 | |
| 0.81.2 | 10 / 3 | |
| 0.81.1 | 10 / 3 | |
| 0.81.0 | 10 / 3 | |
| 0.80.12 | 9 / 3 | |
| 0.80.11 | 9 / 3 | |
| 0.80.10 | 9 / 3 | |
| 0.80.9 | 8 / 3 | |
| 0.80.8 | 8 / 3 | |
| 0.80.7 | 8 / 3 | |
| 0.80.6 | 8 / 3 | |
| 0.80.5 | 8 / 3 | |
| 0.80.4 | 8 / 3 | |
| 0.80.3 | 8 / 3 | |
| 0.80.2 | 8 / 3 | |
| 0.80.1 | 8 / 3 | |
| 0.80.0 | 8 / 3 | |
| 0.79.1 | 8 / 3 | |
| 0.79.0 | 8 / 3 | |
| 0.78.1 | 8 / 3 | |
| 0.78.0 | 8 / 3 | |
| 0.77.0 | 8 / 3 | |
| 0.76.9 | 8 / 3 | |
| 0.76.8 | 8 / 3 | |
| 0.76.7 | 8 / 3 | |
| 0.76.6 | 8 / 3 | |
| 0.76.5 | 8 / 3 |
v0.87.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.86.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.82.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.80.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.