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 69 of 169)
| Version | Deps | Published |
|---|---|---|
| 0.59.0 | 1 / 0 | |
| 0.58.0 | 1 / 0 | |
| 0.57.0 | 1 / 0 | |
| 0.56.4 | 1 / 0 | |
| 0.56.3 | 1 / 0 | |
| 0.56.0 | 1 / 0 | |
| 0.55.0 | 1 / 0 | |
| 0.54.1 | 1 / 0 | |
| 0.54.0 | 1 / 0 | |
| 0.53.1 | 1 / 0 | |
| 0.53.0 | 1 / 0 | |
| 0.52.0 | 1 / 0 | |
| 0.51.1 | 1 / 0 | |
| 0.51.0 | 1 / 0 | |
| 0.50.0 | 1 / 0 | |
| 0.49.2 | 1 / 0 | |
| 0.49.1 | 1 / 0 | |
| 0.49.0 | 1 / 0 | |
| 0.48.5 | 1 / 0 | |
| 0.48.4 | 1 / 0 | |
| 0.48.3 | 1 / 0 | |
| 0.48.2 | 1 / 0 | |
| 0.48.1 | 1 / 0 | |
| 0.48.0 | 1 / 0 | |
| 0.47.1 | 1 / 0 | |
| 0.47.0 | 1 / 0 | |
| 0.46.0 | 1 / 0 | |
| 0.45.6 | 1 / 0 | |
| 0.45.5 | 1 / 0 | |
| 0.45.4 | 1 / 0 | |
| 0.45.3 | 1 / 0 | |
| 0.45.2 | 1 / 0 | |
| 0.45.1 | 1 / 0 | |
| 0.45.0 | 1 / 0 | |
| 0.44.0 | 1 / 0 | |
| 0.43.6 | 1 / 0 | |
| 0.43.5 | 1 / 0 | |
| 0.43.4 | 1 / 0 | |
| 0.43.3 | 1 / 0 | |
| 0.43.2 | 1 / 0 | |
| 0.43.1 | 1 / 0 | |
| 0.43.0 | 1 / 0 | |
| 0.42.2 | 1 / 0 | |
| 0.42.1 | 1 / 0 | |
| 0.40.1 | 1 / 0 | |
| 0.40.0 | 1 / 0 | |
| 0.39.1 | 1 / 0 | |
| 0.39.0 | 1 / 0 | |
| 0.38.4 | 1 / 0 | |
| 0.38.3 | 1 / 0 | |
| 0.38.2 | 1 / 0 | |
| 0.38.1 | 1 / 0 | |
| 0.38.0 | 1 / 0 | |
| 0.37.2 | 1 / 0 | |
| 0.37.1 | 1 / 0 | |
| 0.37.0 | 1 / 0 | |
| 0.36.1 | 1 / 0 | |
| 0.36.0 | 1 / 0 | |
| 0.35.0 | 1 / 0 | |
| 0.34.0 | 1 / 0 | |
| 0.33.0 | 1 / 0 | |
| 0.32.0 | 1 / 0 | |
| 0.31.0 | 1 / 0 | |
| 0.30.2 | 1 / 0 | |
| 0.30.1 | 1 / 0 | |
| 0.30.0 | 1 / 0 | |
| 0.29.0 | 1 / 0 | |
| 0.28.0 | 1 / 0 | |
| 0.27.0 | 1 / 0 |
v0.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
2 findingsThis version was published by a different npm account (metro-bot) than the most recent previously approved version (rafeca) on 2019-02-19. It has since remained available on npm for 2709 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.51.1
2 findingsThis version was published by a different npm account (metro-bot) than the most recent previously approved version (rafeca) on 2018-12-21. It has since remained available on npm for 2768 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.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
2 findingsThis version was published by a different npm account (metro-bot) than the most recent previously approved version (rafeca) on 2018-11-29. It has since remained available on npm for 2790 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.49.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rafeca) than the most recent previously approved version (metro-bot) on 2018-12-12, but rafeca is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.48.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.