@lindorm/aes
High-level AES encryption and decryption for Node.js with first-class TypeScript support. `@lindorm/aes` wraps key derivation, key wrapping, and authenticated content encryption behind a single `AesKit` class — encrypt any supported value in one call and
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 |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex literals in test fixtures are AES key constants, not obfuscated payloads; stable false positive for this crypto library. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped @lindorm/aes cannot be a typosquat of jest; levenshtein match is spurious. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @lindorm/aes cannot be a typosquat of qs; levenshtein match is spurious. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped @lindorm/aes cannot be a typosquat of ajv; levenshtein match is spurious. | ai | |
| phantom-deps | phantom-dep:@lindorm/utils | AI (phantom-deps): Same-org sibling dep; may be re-exported or used indirectly via other @lindorm/* packages. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.7.2 | 6 / 2 | |
| 0.7.1 | 6 / 2 | |
| 0.7.0 | 6 / 2 | |
| 0.6.5 | 5 / 3 | |
| 0.6.4 | 5 / 3 | |
| 0.6.3 | 5 / 3 | |
| 0.6.2 | 5 / 3 | |
| 0.6.1 | 5 / 3 | |
| 0.6.0 | 5 / 3 | |
| 0.5.5 | 4 / 1 | |
| 0.5.4 | 4 / 1 | |
| 0.5.3 | 4 / 1 | |
| 0.5.2 | 4 / 1 | |
| 0.5.1 | 4 / 1 | |
| 0.5.0 | 4 / 1 |
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
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.