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 |
|---|---|---|---|---|
| provenance | publisher-changed-stale | AI (provenance): Old publisher change consistent with fb/metro-bot ecosystem tooling, not compromise. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): metro-runtime is first-party sibling package pinned to same version. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same org migration to metro-bot publisher. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Individual maintainer replaced by org bot account, standard transition. | ai | |
| phantom-deps | phantom-dep:pretty-format | AI (phantom-deps): Used in config/test helpers, not a real risk. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Long-standing fb/metro-bot org transition, not a fresh compromise; stable across metro's version history. | ai | |
| 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 | |
| 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 | |
| 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 |
Versions (showing 51 of 143)
| Version | Deps | Published |
|---|---|---|
| 0.87.0 | 7 / 3 | |
| 0.86.0 | 7 / 3 | |
| 0.85.0 | 8 / 3 | |
| 0.84.4 | 8 / 3 | |
| 0.84.3 | 8 / 3 | |
| 0.84.2 | 8 / 3 | |
| 0.84.1 | 8 / 3 | |
| 0.84.0 | 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.82.1 | 8 / 3 | |
| 0.82.0 | 8 / 3 | |
| 0.81.5 | 8 / 3 | |
| 0.81.4 | 8 / 3 | |
| 0.81.3 | 8 / 3 | |
| 0.81.2 | 8 / 3 | |
| 0.81.1 | 8 / 3 | |
| 0.81.0 | 8 / 4 | |
| 0.80.12 | 8 / 4 | |
| 0.80.11 | 8 / 4 | |
| 0.80.10 | 8 / 4 | |
| 0.80.9 | 7 / 3 | |
| 0.80.8 | 7 / 3 | |
| 0.80.7 | 7 / 3 | |
| 0.80.6 | 7 / 3 | |
| 0.80.5 | 7 / 3 | |
| 0.80.4 | 7 / 3 | |
| 0.80.3 | 7 / 3 | |
| 0.80.2 | 7 / 3 | |
| 0.80.1 | 7 / 3 | |
| 0.80.0 | 7 / 3 | |
| 0.79.1 | 7 / 3 | |
| 0.79.0 | 7 / 3 | |
| 0.78.1 | 7 / 3 | |
| 0.78.0 | 7 / 3 | |
| 0.77.0 | 7 / 3 | |
| 0.76.9 | 7 / 3 | |
| 0.76.8 | 7 / 3 | |
| 0.76.7 | 7 / 3 | |
| 0.76.6 | 7 / 3 | |
| 0.76.5 | 6 / 2 |
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.84.2
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (metro-bot) on 2026-02-27, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.84.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.84.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (metro-bot) on 2026-02-20, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
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.