@dedot/api
A delightful JavaScript/TypeScript client for Polkadot & Substrate
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped @dedot/* package for Polkadot ecosystem; no relation to hapi. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @dedot/* package; Levenshtein match to pg is noise. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @dedot/* package; Levenshtein match to joi is noise. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped @dedot/* package; Levenshtein match to ajv is noise. | ai | |
| dependencies | unvetted-dep:@dedot/shape | AI (dependencies): First-party sibling package in the @dedot monorepo. | ai | |
| dependencies | unvetted-dep:@dedot/types | AI (dependencies): First-party sibling package in the @dedot monorepo. | ai | |
| dependencies | unvetted-dep:@dedot/codecs | AI (dependencies): First-party sibling package in the @dedot monorepo. | ai | |
| dependencies | unvetted-dep:@dedot/providers | AI (dependencies): First-party sibling package in the @dedot monorepo. | ai | |
| dependencies | unvetted-dep:@dedot/runtime-specs | AI (dependencies): First-party sibling package in the @dedot monorepo. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.3.0 | 7 / 0 | |
| 1.2.0 | 7 / 0 | |
| 1.1.1 | 7 / 0 | |
| 1.0.4 | 7 / 0 | |
| 1.0.3 | 7 / 0 | |
| 1.0.2 | 7 / 0 | |
| 1.0.1 | 7 / 0 | |
| 1.0.0 | 7 / 0 | |
| 0.18.8 | 7 / 0 | |
| 0.18.7 | 7 / 0 | |
| 0.18.6 | 7 / 0 |
v1.3.0
2 findingsPackage name '@dedot/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.