@lucid-evolution/lucid
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@lucid-evolution/wallet | AI (dependencies): First-party @lucid-evolution monorepo package; same publisher, stable track record. | ai | |
| dependencies | unvetted-dep:@lucid-evolution/tx-graph | AI (dependencies): First-party @lucid-evolution monorepo package; same publisher, same release. | ai | |
| dependencies | unvetted-dep:@anastasia-labs/cardano-multiplatform-lib-nodejs | AI (dependencies): Known Cardano ecosystem lib from the same org (Anastasia-Labs); stable dependency. | ai | |
| dependencies | unvetted-dep:@anastasia-labs/cardano-multiplatform-lib-browser | AI (dependencies): Known Cardano ecosystem lib from the same org (Anastasia-Labs); stable dependency. | ai | |
| phantom-deps | phantom-dep:@emurgo/cardano-message-signing-nodejs | AI (phantom-deps): Declared for conditional browser/node resolution via package.json browser field, not a phantom dep. | ai | |
| phantom-deps | phantom-dep:@anastasia-labs/cardano-multiplatform-lib-browser | AI (phantom-deps): Declared as browser-field alias for the nodejs variant; expected pattern for this package. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped package @lucid-evolution/lucid is not a typosquat of uuid; Levenshtein match is a false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 14 / 9 | |
| 0.4.34 | 13 / 8 | |
| 0.4.33 | 13 / 8 | |
| 0.4.32 | 13 / 8 | |
| 0.4.31 | 13 / 8 | |
| 0.4.30 | 13 / 8 |
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.