@techteamer/ocsp
OCSP Stapling implementation
1
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
tgabi333tunderdombtbence
Keywords
OCSPASN.1Stapling
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in this context is standard PEM-to-DER certificate parsing, a core requirement of any OCSP/X.509 library. Not a malicious payload. | ai | |
| dependencies | unvetted-dep:simple-lru-cache | AI (dependencies): simple-lru-cache is a small, long-standing npm utility; its use for caching OCSP responses is appropriate and expected for this library. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 5 / 4 |
v1.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.