@wildboar/pkcs
Public Key Cryptography Standard PDUs in TypeScript
3
Versions
MIT
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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
jonathanwilbur
Keywords
pkcspublickeycryptographystandardcryptorsacsrpfx
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with consistent publisher; lack of Sigstore attestation is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@wildboar/cms | AI (phantom-deps): JSR alias pattern; declared as npm:@jsr/wildboar__cms, phantom-dep fires due to alias resolution mismatch. | ai | |
| phantom-deps | phantom-dep:@wildboar/ldap | AI (phantom-deps): JSR alias pattern; same false-positive cause as @wildboar/cms. | ai | |
| phantom-deps | phantom-dep:@wildboar/pki-stub | AI (phantom-deps): JSR alias pattern; same false-positive cause as @wildboar/cms. | ai |
v2.0.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.