metro-resolver
🚇 Implementation of Metro's resolution logic.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are known Facebook/metro-bot accounts. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consolidation to metro-bot, consistent with org's release automation. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Publisher rotation within Meta's metro org, stable for years on npm. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): invariant is a trivial, ubiquitous FB-authored utility dep. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Long-lived official facebook/metro package; fb/metro-bot is expected org maintainer pattern, not hijack. | ai |
Versions (showing 100 of 169)
| Version | Deps | Published |
|---|---|---|
| 0.87.0 | 1 / 1 | |
| 0.86.0 | 1 / 1 | |
| 0.85.0 | 1 / 1 | |
| 0.84.4 | 1 / 1 | |
| 0.84.3 | 1 / 1 | |
| 0.84.2 | 1 / 1 | |
| 0.84.1 | 1 / 1 | |
| 0.84.0 | 1 / 1 | |
| 0.83.7 | 1 / 1 | |
| 0.83.6 | 1 / 1 | |
| 0.83.5 | 1 / 1 | |
| 0.83.4 | 1 / 1 | |
| 0.83.3 | 1 / 1 | |
| 0.83.2 | 1 / 1 | |
| 0.83.1 | 1 / 1 | |
| 0.83.0 | 1 / 1 | |
| 0.82.5 | 1 / 1 | |
| 0.82.4 | 1 / 1 | |
| 0.82.3 | 1 / 1 | |
| 0.82.2 | 1 / 1 | |
| 0.82.1 | 1 / 1 | |
| 0.82.0 | 1 / 1 | |
| 0.81.5 | 1 / 1 | |
| 0.81.4 | 1 / 1 | |
| 0.81.3 | 1 / 1 | |
| 0.81.2 | 1 / 1 | |
| 0.81.1 | 1 / 1 | |
| 0.81.0 | 1 / 1 | |
| 0.80.12 | 1 / 1 | |
| 0.80.11 | 1 / 1 | |
| 0.80.10 | 1 / 1 | |
| 0.80.9 | 0 / 1 | |
| 0.80.8 | 0 / 1 | |
| 0.80.7 | 0 / 1 | |
| 0.80.6 | 0 / 1 | |
| 0.80.5 | 0 / 1 | |
| 0.80.4 | 0 / 1 | |
| 0.80.3 | 0 / 1 | |
| 0.80.2 | 0 / 1 | |
| 0.80.1 | 0 / 1 | |
| 0.80.0 | 0 / 1 | |
| 0.79.1 | 0 / 1 | |
| 0.79.0 | 0 / 1 | |
| 0.78.1 | 0 / 1 | |
| 0.78.0 | 0 / 1 | |
| 0.77.0 | 0 / 0 | |
| 0.76.9 | 0 / 0 | |
| 0.76.8 | 0 / 0 | |
| 0.76.7 | 0 / 0 | |
| 0.76.6 | 0 / 0 | |
| 0.76.5 | 0 / 0 | |
| 0.76.4 | 0 / 0 | |
| 0.76.3 | 0 / 0 | |
| 0.76.2 | 0 / 0 | |
| 0.76.1 | 0 / 0 | |
| 0.76.0 | 0 / 0 | |
| 0.75.1 | 2 / 0 | |
| 0.75.0 | 1 / 0 | |
| 0.74.1 | 1 / 0 | |
| 0.74.0 | 1 / 0 | |
| 0.73.10 | 1 / 0 | |
| 0.73.9 | 1 / 0 | |
| 0.73.8 | 1 / 0 | |
| 0.73.7 | 1 / 0 | |
| 0.73.6 | 1 / 0 | |
| 0.73.5 | 1 / 0 | |
| 0.73.4 | 1 / 0 | |
| 0.73.3 | 1 / 0 | |
| 0.73.2 | 1 / 0 | |
| 0.73.1 | 1 / 0 | |
| 0.73.0 | 1 / 0 | |
| 0.72.4 | 1 / 0 | |
| 0.72.3 | 1 / 0 | |
| 0.72.2 | 1 / 0 | |
| 0.72.1 | 1 / 0 | |
| 0.72.0 | 1 / 0 | |
| 0.71.3 | 1 / 0 | |
| 0.71.2 | 1 / 0 | |
| 0.71.1 | 1 / 0 | |
| 0.71.0 | 1 / 0 | |
| 0.70.4 | 1 / 0 | |
| 0.70.3 | 1 / 0 | |
| 0.70.2 | 1 / 0 | |
| 0.70.1 | 1 / 0 | |
| 0.70.0 | 1 / 0 | |
| 0.69.1 | 1 / 0 | |
| 0.69.0 | 1 / 0 | |
| 0.68.0 | 1 / 0 | |
| 0.67.0 | 1 / 0 | |
| 0.66.2 | 1 / 0 | |
| 0.66.1 | 1 / 0 | |
| 0.66.0 | 1 / 0 | |
| 0.65.2 | 1 / 0 | |
| 0.65.1 | 1 / 0 | |
| 0.65.0 | 1 / 0 | |
| 0.64.0 | 1 / 0 | |
| 0.63.0 | 1 / 0 | |
| 0.62.0 | 1 / 0 | |
| 0.61.0 | 1 / 0 | |
| 0.60.0 | 1 / 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.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.
v0.76.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.66.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.66.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.64.0
2 findingsThis version was published by a different npm account (cpojer) than the most recent previously approved version (metro-bot) on 2020-11-05. It has since remained available on npm for 2084 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.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.