metro-config
🚇 Config parser 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:metro | AI (dependencies): metro is a monorepo sibling at the same version; co-versioned dependency is expected and stable across releases. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in loadConfig.js is intentional — it loads user-specified Metro config files by absolute path. This is the documented behavior of a config parser, not a security risk. | ai | |
| phantom-deps | phantom-dep:flow-enums-runtime | AI (phantom-deps): flow-enums-runtime is a legitimate runtime dependency declared in package.json; the phantom-dep flag is a false positive from Flow-compiled code import patterns. | ai | |
| bogus-package | bogus-package | AI (bogus-package): metro-config is a monorepo sub-package of facebook/metro; sparse README and no keywords are expected for internal sub-packages, not spam indicators. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.84.4 | 8 / 3 | |
| 0.84.3 | 8 / 3 | |
| 0.83.7 | 8 / 3 | |
| 0.83.6 | 8 / 3 | |
| 0.83.5 | 8 / 3 | |
| 0.83.4 | 8 / 3 | |
| 0.83.3 | 8 / 3 | |
| 0.83.2 | 8 / 3 | |
| 0.83.1 | 8 / 3 | |
| 0.83.0 | 8 / 3 | |
| 0.82.5 | 8 / 3 | |
| 0.82.4 | 8 / 3 | |
| 0.82.3 | 8 / 3 | |
| 0.82.2 | 8 / 3 | |
| 0.81.5 | 8 / 3 |
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.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
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.