@lindorm/aegis
JOSE token operations for JWT, JWS, and JWE backed by an Amphora key store.
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:cbor | AI (phantom-deps): cbor is declared in dependencies and used by the package; phantom-dep heuristic misfired. | ai | |
| typosquat | typosquat.levenshtein:redis | AI (typosquat): Part of the lindorm-io monorepo; name similarity to redis is coincidental, not a squatting attempt. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.8.1 | 15 / 6 | |
| 0.8.0 | 15 / 6 | |
| 0.7.2 | 15 / 6 | |
| 0.5.0 | 13 / 7 | |
| 0.4.4 | 12 / 7 | |
| 0.4.3 | 12 / 7 | |
| 0.4.2 | 12 / 7 | |
| 0.4.1 | 12 / 7 | |
| 0.4.0 | 12 / 7 | |
| 0.3.6 | 12 / 5 | |
| 0.3.5 | 12 / 5 | |
| 0.3.4 | 12 / 5 | |
| 0.3.3 | 12 / 5 | |
| 0.3.2 | 12 / 5 | |
| 0.3.1 | 12 / 5 | |
| 0.3.0 | 12 / 5 |
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
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.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.