@reyaxyz/api-sdk
<p align="center"> API sdk for the Reya Network </p>
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:ws | AI (phantom-deps): ws is a declared runtime dep used via isomorphic-ws abstraction; phantom-dep is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): axios is a declared runtime dep; indirect usage pattern is stable for this SDK package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse README/keywords are cosmetic; package is a well-established SDK with 814 versions. | ai | |
| phantom-deps | phantom-dep:@simplewebauthn/types | AI (phantom-deps): Type-only dependency; not directly imported at runtime is expected for @types-style packages. | ai | |
| typosquat | typosquat.levenshtein:aws-sdk | AI (typosquat): Scoped @reyaxyz package; Levenshtein match to aws-sdk is coincidental, not impersonation. | ai | |
| semgrep | semgrep:shady-links-tlds | AI (semgrep): URL is api.reya.xyz — the package's own API endpoint, not a C2/exfiltration domain. | ai |
Versions (showing 45 of 248)
| Version | Deps | Published |
|---|---|---|
| 0.153.31 | 7 / 1 | |
| 0.153.30 | 7 / 1 | |
| 0.153.29 | 7 / 1 | |
| 0.153.28 | 7 / 1 | |
| 0.153.27 | 7 / 1 | |
| 0.153.26 | 7 / 1 | |
| 0.153.25 | 7 / 1 | |
| 0.153.24 | 7 / 1 | |
| 0.153.23 | 7 / 1 | |
| 0.153.22 | 7 / 1 | |
| 0.153.21 | 7 / 1 | |
| 0.153.20 | 7 / 1 | |
| 0.153.19 | 7 / 1 | |
| 0.153.18 | 7 / 1 | |
| 0.153.17 | 7 / 1 | |
| 0.153.16 | 7 / 1 | |
| 0.153.15 | 7 / 1 | |
| 0.153.14 | 7 / 1 | |
| 0.153.13 | 7 / 1 | |
| 0.153.12 | 7 / 1 | |
| 0.153.11 | 7 / 1 | |
| 0.153.10 | 7 / 1 | |
| 0.153.9 | 7 / 1 | |
| 0.153.8 | 7 / 1 | |
| 0.153.7 | 7 / 1 | |
| 0.153.6 | 7 / 1 | |
| 0.153.5 | 7 / 1 | |
| 0.153.4 | 7 / 1 | |
| 0.153.3 | 7 / 1 | |
| 0.153.2 | 7 / 1 | |
| 0.153.1 | 7 / 1 | |
| 0.153.0 | 7 / 1 | |
| 0.152.8 | 7 / 1 | |
| 0.152.7 | 7 / 1 | |
| 0.152.6 | 7 / 1 | |
| 0.152.5 | 7 / 1 | |
| 0.152.4 | 7 / 1 | |
| 0.152.3 | 7 / 1 | |
| 0.152.2 | 7 / 1 | |
| 0.152.1 | 7 / 1 | |
| 0.152.0 | 7 / 1 | |
| 0.151.22 | 7 / 1 | |
| 0.151.21 | 7 / 1 | |
| 0.151.20 | 7 / 1 | |
| 0.151.19 | 7 / 1 |
v0.153.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.153.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.152.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.152.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.152.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.152.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.152.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.152.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.152.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.152.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.152.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.151.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.151.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.151.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.151.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.