metro-symbolicate
🚇 A tool to find the source location from JS bundles and stack traces.
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): Same historical transfer, long-stable, not a fresh compromise signal. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Deps are standard/well-known and match metro's own sibling packages. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Known motiz88→facebook org transfer; live 2699d, matches official repo. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process only in test harness (spawn), not runtime payload. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing is backed by SLSA Sigstore attestation; consistent with Meta/Facebook's CI pipeline migration. | ai | |
| phantom-deps | phantom-dep:flow-enums-runtime | AI (phantom-deps): flow-enums-runtime is a declared dep used via Flow type system config, not a direct JS import; stable false positive for this package. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 0.87.0 | 6 / 0 | |
| 0.86.0 | 6 / 0 | |
| 0.85.0 | 6 / 0 | |
| 0.84.4 | 6 / 0 | |
| 0.84.3 | 6 / 0 | |
| 0.84.2 | 6 / 0 | |
| 0.84.1 | 6 / 0 | |
| 0.84.0 | 6 / 0 | |
| 0.83.7 | 6 / 0 | |
| 0.83.6 | 6 / 0 | |
| 0.83.5 | 6 / 0 | |
| 0.83.4 | 6 / 0 | |
| 0.83.3 | 6 / 0 | |
| 0.83.2 | 6 / 0 | |
| 0.83.1 | 6 / 0 | |
| 0.83.0 | 6 / 0 | |
| 0.82.5 | 6 / 0 | |
| 0.82.4 | 6 / 0 | |
| 0.82.3 | 6 / 0 | |
| 0.82.2 | 6 / 0 | |
| 0.82.1 | 6 / 0 | |
| 0.82.0 | 6 / 0 | |
| 0.81.5 | 6 / 0 | |
| 0.81.4 | 6 / 0 | |
| 0.81.3 | 6 / 0 | |
| 0.81.2 | 6 / 0 | |
| 0.81.1 | 6 / 0 | |
| 0.81.0 | 7 / 0 | |
| 0.80.12 | 7 / 0 | |
| 0.80.11 | 7 / 0 | |
| 0.80.10 | 7 / 0 | |
| 0.80.9 | 6 / 0 | |
| 0.73.4 | 6 / 0 | |
| 0.56.0 | 5 / 0 | |
| 0.53.0 | 3 / 0 | |
| 0.52.0 | 0 / 0 |
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.73.4
2 findingsThis version was published by a different npm account (metro-bot) than the most recent previously approved version (motiz88) on 2022-12-01. It has since remained available on npm for 1328 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.56.0
2 findingsThis version was published by a different npm account (metro-bot) than the most recent previously approved version (motiz88) on 2019-08-12. It has since remained available on npm for 2535 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.53.0
3 findingschild_process imported — can execute arbitrary system commands 13 | const fs = require('fs'); 14 | const path = require('path'); > 15 | const {spawn} = require('child_process'); 16 | 17 | const resolve = fileName => path.resolve(__dirname, '__fixtures__', fileName);
This version was published by a different npm account (metro-bot) than the most recent previously approved version (motiz88) on 2019-03-01. It has since remained available on npm for 2699 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.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.