selfsigned
Generate self signed certificates private and public keys
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process usage is confined to an examples/ file (https-server-mkcert.js), not the library runtime. Not a risk for consumers of this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in index.js is standard PEM-to-DER conversion for certificate handling — expected and benign for a self-signed cert library. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 5.5.0 | 2 / 2 | |
| 5.4.0 | 2 / 2 | |
| 5.2.0 | 2 / 2 | |
| 5.1.0 | 2 / 2 | |
| 5.0.0 | 2 / 2 | |
| 4.0.1 | 1 / 3 | |
| 2.4.1 | 2 / 2 |
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.