metro-core
🚇 Metro's core package.
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 | missing-githead | AI (provenance): Known Metro CI publish env; gitHead absence is not malicious for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): jest-haste-map is an established first-party dep; normal for Metro. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Known legitimate package; 0.0.0 is a placeholder publish, not malicious throwaway. | ai | |
| bogus-package | bogus-package | AI (bogus-package): metro-core 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 standard transitive requirement for Flow-typed packages; its presence as a declared dep without direct import is normal for this package family. | ai |
Versions (showing 100 of 181)
| Version | Deps | Published |
|---|---|---|
| 0.87.0 | 3 / 0 | |
| 0.86.0 | 3 / 0 | |
| 0.85.0 | 3 / 0 | |
| 0.84.4 | 3 / 0 | |
| 0.84.3 | 3 / 0 | |
| 0.84.2 | 3 / 0 | |
| 0.84.1 | 3 / 0 | |
| 0.84.0 | 3 / 0 | |
| 0.83.7 | 3 / 0 | |
| 0.83.6 | 3 / 0 | |
| 0.83.5 | 3 / 0 | |
| 0.83.4 | 3 / 0 | |
| 0.83.3 | 3 / 0 | |
| 0.83.2 | 3 / 0 | |
| 0.83.1 | 3 / 0 | |
| 0.83.0 | 3 / 0 | |
| 0.82.5 | 3 / 0 | |
| 0.82.4 | 3 / 0 | |
| 0.82.3 | 3 / 0 | |
| 0.82.2 | 3 / 0 | |
| 0.82.1 | 3 / 0 | |
| 0.82.0 | 3 / 0 | |
| 0.81.5 | 3 / 0 | |
| 0.81.4 | 3 / 0 | |
| 0.81.3 | 3 / 0 | |
| 0.81.2 | 3 / 0 | |
| 0.81.1 | 3 / 0 | |
| 0.81.0 | 3 / 0 | |
| 0.80.12 | 3 / 0 | |
| 0.80.11 | 3 / 0 | |
| 0.80.10 | 3 / 0 | |
| 0.80.9 | 2 / 0 | |
| 0.80.8 | 2 / 0 | |
| 0.80.7 | 2 / 0 | |
| 0.80.6 | 2 / 0 | |
| 0.80.5 | 2 / 0 | |
| 0.80.4 | 2 / 0 | |
| 0.80.3 | 2 / 0 | |
| 0.80.2 | 2 / 0 | |
| 0.80.1 | 2 / 0 | |
| 0.80.0 | 2 / 0 | |
| 0.79.1 | 2 / 0 | |
| 0.79.0 | 2 / 0 | |
| 0.78.1 | 2 / 0 | |
| 0.78.0 | 2 / 0 | |
| 0.77.0 | 2 / 0 | |
| 0.76.9 | 2 / 0 | |
| 0.76.8 | 2 / 0 | |
| 0.76.7 | 2 / 0 | |
| 0.76.6 | 2 / 0 | |
| 0.76.5 | 2 / 0 | |
| 0.76.4 | 2 / 0 | |
| 0.76.3 | 2 / 0 | |
| 0.76.2 | 2 / 0 | |
| 0.76.1 | 2 / 0 | |
| 0.76.0 | 2 / 0 | |
| 0.75.1 | 2 / 0 | |
| 0.75.0 | 2 / 0 | |
| 0.74.1 | 2 / 0 | |
| 0.74.0 | 2 / 0 | |
| 0.73.10 | 2 / 0 | |
| 0.73.9 | 2 / 0 | |
| 0.73.8 | 2 / 0 | |
| 0.73.7 | 2 / 0 | |
| 0.73.6 | 2 / 0 | |
| 0.73.5 | 2 / 0 | |
| 0.73.4 | 2 / 0 | |
| 0.73.3 | 2 / 0 | |
| 0.73.2 | 2 / 0 | |
| 0.73.1 | 2 / 0 | |
| 0.73.0 | 2 / 0 | |
| 0.72.4 | 2 / 0 | |
| 0.72.3 | 2 / 0 | |
| 0.72.2 | 2 / 0 | |
| 0.72.1 | 2 / 0 | |
| 0.72.0 | 2 / 0 | |
| 0.71.3 | 2 / 0 | |
| 0.71.2 | 2 / 0 | |
| 0.71.1 | 2 / 0 | |
| 0.71.0 | 2 / 0 | |
| 0.70.4 | 3 / 0 | |
| 0.70.3 | 3 / 0 | |
| 0.70.2 | 3 / 0 | |
| 0.70.1 | 3 / 0 | |
| 0.70.0 | 3 / 0 | |
| 0.69.1 | 3 / 0 | |
| 0.69.0 | 3 / 0 | |
| 0.68.0 | 3 / 0 | |
| 0.67.0 | 3 / 0 | |
| 0.66.2 | 3 / 0 | |
| 0.66.1 | 3 / 0 | |
| 0.66.0 | 3 / 0 | |
| 0.65.2 | 3 / 0 | |
| 0.65.1 | 3 / 0 | |
| 0.65.0 | 3 / 0 | |
| 0.64.0 | 3 / 0 | |
| 0.63.0 | 3 / 0 | |
| 0.62.0 | 3 / 0 | |
| 0.61.0 | 3 / 0 | |
| 0.60.0 | 3 / 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.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
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: metro-bot.
Package 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
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: metro-bot.
Package 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 2082 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
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 (metro-bot) than the most recent previously approved version (cpojer) on 2020-07-21, but metro-bot 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.60.0
2 findingsThis version was published by a different npm account (cpojer) than the most recent previously approved version (metro-bot) on 2020-06-30. It has since remained available on npm for 2209 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.