@rialo/ts-cdk
Rialo CDK - A comprehensive toolkit for building with the Rialo blockchain
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:@dao-xyz/borsh | AI (dependencies): @dao-xyz/borsh is a well-known Borsh serialization library for JS; no known advisories and stable use in this CDK context. | ai | |
| phantom-deps | phantom-dep:@dao-xyz/borsh | AI (phantom-deps): Dependency is declared and used transitively/re-exported in CDK bundle; not a true phantom. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions CI; absence of Sigstore attestation is common and not a risk signal for this package. | ai | |
| phantom-deps | phantom-dep:@noble/curves | AI (phantom-deps): Well-known @noble library; declared as direct dep, phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@noble/hashes | AI (phantom-deps): Well-known @noble library; declared as direct dep, phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@scure/base | AI (phantom-deps): Well-known @scure library; declared as direct dep, phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:ed25519-hd-key | AI (phantom-deps): Declared as direct dep in package.json; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@noble/ed25519 | AI (phantom-deps): Well-known @noble library; declared as direct dep, phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@scure/bip32 | AI (phantom-deps): Well-known @scure library; declared as direct dep, phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@scure/bip39 | AI (phantom-deps): Well-known @scure library; declared as direct dep, phantom-dep heuristic false positive for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.4.2 | 10 / 6 | |
| 0.4.1 | 10 / 6 | |
| 0.3.0 | 10 / 6 | |
| 0.2.0 | 8 / 6 | |
| 0.1.10 | 8 / 6 | |
| 0.1.9 | 8 / 6 | |
| 0.1.8 | 8 / 6 | |
| 0.1.5 | 8 / 6 | |
| 0.1.4 | 8 / 6 | |
| 0.1.3 | 8 / 6 | |
| 0.1.2 | 8 / 6 | |
| 0.1.1 | 8 / 6 | |
| 0.1.0 | 8 / 6 |
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.