@swtc/keypairs
swtc keypairs
4
Versions
ISC
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
lospringliu
Keywords
swtcjingtumkeypair
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:elliptic | AI (dependencies): Standard EC crypto library, expected for a keypairs package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Deps are well-known crypto libs fitting the package's purpose. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating Sigstore; no provenance is expected for this ecosystem/age. | ai |
v1.0.10
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.