@criipto/signatures
A Node.JS SDK for Criipto Signatures
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is confirmed by SLSA provenance attestation; legitimate CI/CD migration. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 1.35.1 | 3 / 5 | |
| 1.35.0 | 3 / 5 | |
| 1.34.0 | 3 / 5 | |
| 1.33.0 | 3 / 5 | |
| 1.32.0 | 3 / 5 | |
| 1.31.0 | 3 / 5 | |
| 1.30.0 | 3 / 5 | |
| 1.29.2 | 3 / 5 | |
| 1.29.1 | 3 / 5 | |
| 1.29.0 | 3 / 5 | |
| 1.28.1 | 3 / 5 | |
| 1.28.0 | 3 / 5 | |
| 1.27.1 | 3 / 5 | |
| 1.27.0 | 3 / 5 | |
| 1.26.1 | 3 / 5 | |
| 1.26.0 | 3 / 5 | |
| 1.25.1 | 3 / 5 | |
| 1.25.0 | 3 / 5 | |
| 1.24.1 | 3 / 5 | |
| 1.24.0 | 3 / 5 | |
| 1.23.0 | 3 / 5 | |
| 1.22.4 | 3 / 5 | |
| 1.22.3 | 3 / 5 | |
| 1.22.2 | 3 / 5 | |
| 1.22.0 | 3 / 5 | |
| 1.21.2 | 3 / 5 | |
| 1.21.1 | 3 / 5 | |
| 1.21.0 | 3 / 5 | |
| 1.20.0 | 3 / 5 | |
| 1.19.1 | 3 / 5 | |
| 1.19.0 | 3 / 5 | |
| 1.10.1 | 3 / 9 | |
| 1.10.0 | 3 / 9 | |
| 1.9.0 | 3 / 9 | |
| 1.8.1 | 3 / 9 | |
| 1.8.0 | 3 / 9 | |
| 1.7.1 | 3 / 9 | |
| 1.7.0 | 3 / 9 |
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.