@cipherstash/protect
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 | no-provenance | AI (provenance): CipherStash org package; no provenance is consistent across their published versions. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is explicitly declared as a direct runtime dependency in package.json; phantom-dep finding is a false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 11.1.2 | 6 / 8 | |
| 11.1.1 | 6 / 8 | |
| 11.1.0 | 6 / 8 | |
| 10.2.0 | 4 / 8 | |
| 10.1.0 | 4 / 8 | |
| 10.0.2 | 4 / 8 |
v11.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.