@certd/acme-client
Simple and unopinionated ACME client
1
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
greper
Keywords
acmeclientletsencryptacmev2boulder
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Used in TLS-ALPN ACME challenge construction; standard crypto operation, not obfuscation. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Used for HMAC key decoding in ACME HTTP request signing; standard and expected. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic false positive for ESM imports. | ai | |
| phantom-deps | phantom-dep:punycode.js | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:http-proxy-agent | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:https-proxy-agent | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic false positive. | ai |
Versions (showing 1 of 102)
| Version | Deps | Published |
|---|---|---|
| 1.34.0 | 10 / 15 |
v1.34.0
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.