@neovici/cosmoz-router
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lit | AI (phantom-deps): lit is a declared runtime dependency in package.json; phantom-dep heuristic misfires here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 11.3.0 | 3 / 17 | |
| 11.2.8 | 3 / 21 | |
| 11.2.7 | 3 / 21 | |
| 11.2.6 | 3 / 21 | |
| 11.2.5 | 3 / 22 | |
| 11.2.4 | 1 / 22 | |
| 11.2.3 | 1 / 22 |
v11.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.