metro-cache-key
🚇 Cache key utility.
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 |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): 534B→2KB on a tiny cache-key util is trivial, not a payload. | ai | |
| provenance | missing-githead | AI (provenance): Official Metro release-bot publish flow; gitHead absence is benign metadata drift. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Metro monorepo packages consistently use 0.0.0 as placeholder version; benign convention. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from metro-bot to GitHub Actions CI publishing with SLSA attestation; consistent with Meta's CI/CD migration. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by Meta's publishing pipeline change; SLSA provenance confirms legitimate CI origin. | ai | |
| phantom-deps | phantom-dep:flow-enums-runtime | AI (phantom-deps): flow-enums-runtime is a declared runtime dep used via Flow config; stable false positive for this package. | ai |
Versions (showing 51 of 98)
| 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 / 1 | |
| 0.76.9 | 0 / 1 | |
| 0.76.8 | 0 / 1 | |
| 0.76.7 | 0 / 1 | |
| 0.76.6 | 0 / 1 | |
| 0.76.5 | 0 / 1 |
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.