@reyaxyz/common
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Standard Ethereum message hash hex-decoding via Buffer.from; no malicious payload. | ai | |
| semgrep | semgrep:shady-links-tlds | AI (semgrep): api.reya.xyz is the package's own API endpoint; .xyz TLD is the publisher's registered domain, not C2. | ai |
Versions (showing 100 of 439)
| Version | Deps | Published |
|---|---|---|
| 0.299.0 | 5 / 2 | |
| 0.298.0 | 5 / 2 | |
| 0.297.1 | 5 / 2 | |
| 0.297.0 | 5 / 2 | |
| 0.296.1 | 5 / 2 | |
| 0.296.0 | 5 / 2 | |
| 0.295.1 | 5 / 2 | |
| 0.295.0 | 5 / 2 | |
| 0.294.0 | 5 / 2 | |
| 0.293.3 | 5 / 2 | |
| 0.293.2 | 5 / 2 | |
| 0.293.1 | 5 / 2 | |
| 0.293.0 | 5 / 2 | |
| 0.292.1 | 5 / 2 | |
| 0.292.0 | 5 / 2 | |
| 0.291.9 | 5 / 2 | |
| 0.291.8 | 5 / 2 | |
| 0.291.7 | 5 / 2 | |
| 0.291.6 | 5 / 2 | |
| 0.291.5 | 5 / 2 | |
| 0.291.4 | 5 / 2 | |
| 0.291.3 | 5 / 2 | |
| 0.291.2 | 5 / 2 | |
| 0.291.1 | 5 / 2 | |
| 0.291.0 | 5 / 2 | |
| 0.290.0 | 5 / 2 | |
| 0.289.1 | 5 / 2 | |
| 0.289.0 | 5 / 2 | |
| 0.288.0 | 5 / 2 | |
| 0.287.0 | 5 / 2 | |
| 0.286.2 | 5 / 2 | |
| 0.286.1 | 5 / 2 | |
| 0.286.0 | 5 / 2 | |
| 0.285.0 | 5 / 2 | |
| 0.284.0 | 5 / 2 | |
| 0.283.0 | 5 / 2 | |
| 0.282.0 | 5 / 2 | |
| 0.281.0 | 5 / 2 | |
| 0.280.0 | 5 / 2 | |
| 0.279.0 | 5 / 2 | |
| 0.278.1 | 5 / 2 | |
| 0.278.0 | 5 / 2 | |
| 0.277.1 | 5 / 2 | |
| 0.277.0 | 5 / 2 | |
| 0.276.0 | 5 / 2 | |
| 0.275.0 | 5 / 2 | |
| 0.274.4 | 5 / 2 | |
| 0.274.3 | 5 / 2 | |
| 0.274.2 | 5 / 2 | |
| 0.274.1 | 5 / 2 | |
| 0.274.0 | 5 / 2 | |
| 0.273.1 | 5 / 2 | |
| 0.273.0 | 5 / 2 | |
| 0.272.1 | 5 / 2 | |
| 0.272.0 | 5 / 2 | |
| 0.271.0 | 5 / 2 | |
| 0.270.0 | 5 / 2 | |
| 0.269.0 | 5 / 2 | |
| 0.268.3 | 5 / 2 | |
| 0.268.2 | 5 / 2 | |
| 0.268.1 | 5 / 2 | |
| 0.268.0 | 5 / 2 | |
| 0.267.0 | 5 / 2 | |
| 0.266.1 | 5 / 2 | |
| 0.266.0 | 5 / 2 | |
| 0.265.0 | 5 / 2 | |
| 0.264.0 | 5 / 2 | |
| 0.263.1 | 5 / 2 | |
| 0.263.0 | 5 / 2 | |
| 0.262.1 | 5 / 2 | |
| 0.262.0 | 5 / 2 | |
| 0.261.1 | 5 / 2 | |
| 0.261.0 | 5 / 2 | |
| 0.260.4 | 5 / 2 | |
| 0.260.3 | 5 / 2 | |
| 0.260.2 | 5 / 2 | |
| 0.260.1 | 5 / 2 | |
| 0.260.0 | 5 / 2 | |
| 0.259.0 | 5 / 2 | |
| 0.258.4 | 5 / 2 | |
| 0.258.3 | 5 / 2 | |
| 0.258.2 | 5 / 2 | |
| 0.258.1 | 5 / 2 | |
| 0.257.0 | 5 / 2 | |
| 0.256.0 | 5 / 2 | |
| 0.255.0 | 5 / 2 | |
| 0.254.1 | 5 / 2 | |
| 0.254.0 | 5 / 2 | |
| 0.253.0 | 5 / 2 | |
| 0.252.0 | 5 / 2 | |
| 0.251.0 | 5 / 2 | |
| 0.250.0 | 5 / 2 | |
| 0.249.1 | 5 / 2 | |
| 0.249.0 | 5 / 2 | |
| 0.248.0 | 5 / 2 | |
| 0.247.0 | 5 / 2 | |
| 0.246.0 | 5 / 2 | |
| 0.245.0 | 5 / 2 | |
| 0.244.0 | 5 / 2 | |
| 0.243.0 | 5 / 2 |
v0.274.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.274.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.274.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.273.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.273.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.272.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.272.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.271.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.270.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.269.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.268.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.268.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.268.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.268.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.267.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.266.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.266.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.265.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.264.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.263.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.263.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.262.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.262.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.261.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.261.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.260.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.260.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.260.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.260.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.260.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.259.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.258.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.258.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.258.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.258.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.257.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.256.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.255.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.254.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.254.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.253.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.252.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.251.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.250.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.249.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.249.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.248.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.247.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.246.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.245.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.244.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.243.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.