@lindorm/kryptos
Generate, import, convert, certify, and dispose JOSE / X.509 cryptographic keys (EC, OKP, RSA, oct, AKP) from a single TypeScript model.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@lindorm/case | AI (phantom-deps): Same-org dependency; likely used transitively or in build tooling within the monorepo. | ai | |
| phantom-deps | phantom-dep:@lindorm/random | AI (phantom-deps): Same-org dependency; likely used transitively or in build tooling within the monorepo. | ai | |
| source-diff | obfuscated-file:dist/__fixtures__/akp-keys.js | AI (source-diff): Test fixture with base64-encoded crypto keys, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/fixtures/kryptos-rsa.js | AI (source-diff): Test fixture with base64-encoded RSA keys, not obfuscated code. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.8.2 | 11 / 1 | |
| 0.8.1 | 11 / 1 | |
| 0.7.0 | 10 / 2 | |
| 0.6.0 | 10 / 2 | |
| 0.5.3 | 9 / 1 | |
| 0.5.2 | 9 / 1 | |
| 0.5.1 | 9 / 1 | |
| 0.5.0 | 9 / 1 | |
| 0.4.5 | 9 / 1 | |
| 0.4.4 | 9 / 1 | |
| 0.4.3 | 9 / 1 | |
| 0.4.2 | 9 / 1 | |
| 0.4.1 | 9 / 1 | |
| 0.4.0 | 9 / 1 |
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.