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:@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 | |
| 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 | |
| semgrep | semgrep:env-spread | AI (semgrep): Passing process.env to jest-worker child processes is standard build-tool behavior for Metro. | 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 | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads user-configured asset plugins by design; documented extension point in 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 |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 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.81.5 | 40 / 14 |
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 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/facebook/metro/blob/01b4ad617f940c01df1616d10562affb879ac25d/src/DeltaBundler/WorkerFarm.js#L66 64 | } 65 | _makeFarm(absoluteWorkerPath, exposedMethods, numWorkers) { > 66 | const env = { 67 | ...process.env, 68 | FORCE_COLOR: 1,
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 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/facebook/metro/blob/1d59131ebf39a5724d722fe7ea8507bf67abb946/src/DeltaBundler/WorkerFarm.js#L66 64 | } 65 | _makeFarm(absoluteWorkerPath, exposedMethods, numWorkers) { > 66 | const env = { 67 | ...process.env, 68 | FORCE_COLOR: 1,
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 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/facebook/metro/blob/61815654746ec99e1361e52309bc345b476af170/src/DeltaBundler/WorkerFarm.js#L66 64 | } 65 | _makeFarm(absoluteWorkerPath, exposedMethods, numWorkers) { > 66 | const env = { 67 | ...process.env, 68 | FORCE_COLOR: 1,
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
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/facebook/metro/blob/3eecb5a80c6d862affb69b858a7027bdf4fcb579/src/DeltaBundler/WorkerFarm.js#L66 64 | } 65 | _makeFarm(absoluteWorkerPath, exposedMethods, numWorkers) { > 66 | const env = { 67 | ...process.env, 68 | FORCE_COLOR: 1,
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.5
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/facebook/metro/blob/5a62201b5685763561f64db9bc6cfcffddbd2671/src/DeltaBundler/WorkerFarm.js#L66 64 | } 65 | _makeFarm(absoluteWorkerPath, exposedMethods, numWorkers) { > 66 | const env = { 67 | ...process.env, 68 | FORCE_COLOR: 1,
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.4
2 findingsSpreading entire process.env into an object — may capture all secrets Source: ssh://[email protected]/facebook/metro/blob/c3318e4b720b9767d34f96ab22741404e6f3cba3/src/DeltaBundler/WorkerFarm.js#L66 64 | } 65 | _makeFarm(absoluteWorkerPath, exposedMethods, numWorkers) { > 66 | const env = { 67 | ...process.env, 68 | FORCE_COLOR: 1,
Package 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. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.83.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.82.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.82.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.82.3
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.