metro
🚇 The JavaScript bundler for React Native.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:file | AI (phantom-deps): Legacy declared dep, no malicious behavior; stable false positive. | ai | |
| phantom-deps | phantom-dep:coffee-script | AI (phantom-deps): Legacy declared dep, no malicious behavior; stable false positive. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Framework-scoped dep loaded by convention in Metro's transform pipeline. | ai | |
| phantom-deps | phantom-dep:metro-transform-worker | AI (phantom-deps): Sibling monorepo package loaded dynamically by worker path; stable false positive. | ai | |
| phantom-deps | phantom-dep:metro-babel-transformer | AI (phantom-deps): Sibling monorepo package loaded by convention; stable false positive. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Passing process.env to jest-worker child processes is standard build-tool behavior for Metro. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Buffer.from(sha1, 'hex') constructs a cache key from a SHA1 hash — not a malicious payload. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads user-configured asset plugins by design; documented extension point in Metro. | ai | |
| phantom-deps | phantom-dep:source-map | AI (phantom-deps): source-map is a declared runtime dep used transitively via config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:hermes-parser | AI (phantom-deps): hermes-parser is a declared runtime dep used via config/plugin loading; stable false positive for this package. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 0.87.0 | 39 / 17 | |
| 0.86.0 | 39 / 17 | |
| 0.85.0 | 39 / 17 | |
| 0.84.4 | 39 / 17 | |
| 0.84.2 | 40 / 17 | |
| 0.84.1 | 40 / 17 | |
| 0.84.0 | 40 / 16 | |
| 0.83.7 | 39 / 17 | |
| 0.83.6 | 40 / 17 | |
| 0.83.5 | 40 / 17 | |
| 0.83.4 | 40 / 16 | |
| 0.83.3 | 40 / 14 | |
| 0.83.2 | 40 / 14 | |
| 0.83.1 | 40 / 14 | |
| 0.83.0 | 40 / 14 | |
| 0.82.5 | 40 / 14 | |
| 0.82.4 | 40 / 14 | |
| 0.82.3 | 40 / 14 | |
| 0.82.2 | 40 / 13 | |
| 0.82.1 | 40 / 13 | |
| 0.82.0 | 40 / 13 | |
| 0.81.5 | 40 / 14 | |
| 0.81.4 | 40 / 13 | |
| 0.81.3 | 40 / 13 | |
| 0.81.2 | 40 / 13 | |
| 0.81.1 | 40 / 13 | |
| 0.81.0 | 42 / 13 | |
| 0.80.12 | 42 / 13 | |
| 0.80.11 | 42 / 13 | |
| 0.80.10 | 43 / 13 | |
| 0.80.9 | 43 / 13 | |
| 0.80.8 | 43 / 13 | |
| 0.80.7 | 43 / 13 | |
| 0.80.6 | 43 / 13 | |
| 0.80.5 | 43 / 13 | |
| 0.2.0 | 3 / 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.80.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.80.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.80.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.