@reyaxyz/api-sdk MIT 51 versions

@reyaxyz/api-sdk

npm Repository Homepage

<p align="center"> API sdk for the Reya Network </p>

51

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

filip-reyamilanpajovicvoltzprotocol

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	2026/05/18
phantom-deps	phantom-dep:axios	AI (phantom-deps): axios is a declared runtime dep; indirect usage pattern is stable for this SDK package.	ai	2026/05/18
bogus-package	bogus-package	AI (bogus-package): Sparse README/keywords are cosmetic; package is a well-established SDK with 814 versions.	ai	2026/05/05
phantom-deps	phantom-dep:@simplewebauthn/types	AI (phantom-deps): Type-only dependency; not directly imported at runtime is expected for @types-style packages.	ai	2026/04/30
typosquat	typosquat.levenshtein:aws-sdk	AI (typosquat): Scoped @reyaxyz package; Levenshtein match to aws-sdk is coincidental, not impersonation.	ai	2026/04/29
semgrep	semgrep:shady-links-tlds	AI (semgrep): URL is api.reya.xyz — the package's own API endpoint, not a C2/exfiltration domain.	ai	2026/04/29

Versions (showing 51 of 244)

View all versions

Version	Deps	Published
0.166.6	5 / 1	2026-06-04
0.166.5	5 / 1	2026-06-03
0.166.4	5 / 1	2026-06-03
0.166.3	5 / 1	2026-06-03
0.166.2	5 / 1	2026-06-02
0.166.1	5 / 1	2026-05-25
0.166.0	5 / 1	2026-05-25
0.165.4	5 / 1	2026-05-19
0.165.3	5 / 1	2026-05-08
0.165.2	5 / 1	2026-05-06
0.165.1	5 / 1	2026-05-05
0.165.0	5 / 1	2026-05-04
0.164.27	5 / 1	2026-04-30
0.164.26	5 / 1	2026-04-28
0.164.25	5 / 1	2026-04-27
0.164.24	5 / 1	2026-04-23
0.164.23	5 / 1	2026-04-17
0.164.22	5 / 1	2026-04-16
0.164.21	5 / 1	2026-04-13
0.164.20	5 / 1	2026-04-10
0.164.19	5 / 1	2026-04-09
0.164.18	5 / 1	2026-04-06
0.164.17	5 / 1	2026-04-02
0.164.16	5 / 1	2026-03-30
0.164.15	5 / 1	2026-03-27
0.164.14	5 / 1	2026-03-27
0.164.13	5 / 1	2026-03-25
0.164.12	5 / 1	2026-03-24
0.164.11	5 / 1	2026-03-20
0.164.10	5 / 1	2026-03-19
0.164.9	5 / 1	2026-03-18
0.164.8	5 / 1	2026-03-11
0.164.7	5 / 1	2026-03-10
0.164.6	5 / 1	2026-02-26
0.164.5	5 / 1	2026-02-25
0.164.4	5 / 1	2026-02-25
0.164.3	5 / 1	2026-02-23
0.164.2	5 / 1	2026-02-20
0.164.1	5 / 1	2026-02-19
0.164.0	5 / 1	2026-02-19
0.163.18	5 / 1	2026-02-18
0.163.17	5 / 1	2026-02-17
0.163.16	5 / 1	2026-02-13
0.163.15	5 / 1	2026-02-13
0.163.14	5 / 1	2026-02-11
0.163.13	5 / 1	2026-02-10
0.163.11	5 / 1	2026-02-02
0.163.10	5 / 1	2026-01-30
0.163.9	5 / 1	2026-01-30
0.163.8	5 / 1	2026-01-29
0.163.7	5 / 1	2026-01-23

v0.166.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.166.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.166.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.166.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.166.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.166.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.166.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.165.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.165.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.165.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.165.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.165.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.164.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.164.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.164.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.164.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.164.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.164.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.164.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.164.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.164.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.164.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.164.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.164.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.164.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.164.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.164.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.164.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.164.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.164.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.164.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.164.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.164.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.164.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.164.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.164.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.164.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.164.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.164.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.163.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.163.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.163.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.163.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.163.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.163.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.163.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.163.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.163.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.163.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.