@exodus/bytes
Various operations on Uint8Array data
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Package is a bytes/encoding utility; Buffer.from(str, 'base64') is core legitimate functionality, not a malicious payload. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is core functionality of this bytes utility package; the flagged code is a Deno bug detection check, not malicious. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.15.1 | 0 / 43 | |
| 1.15.0 | 0 / 43 | |
| 1.14.1 | 0 / 43 | |
| 1.14.0 | 0 / 43 | |
| 1.13.0 | 0 / 43 | |
| 1.12.0 | 0 / 43 | |
| 1.11.0 | 0 / 42 | |
| 1.10.0 | 0 / 40 | |
| 1.9.0 | 0 / 40 | |
| 1.8.0 | 0 / 36 | |
| 1.7.0 | 0 / 37 | |
| 1.6.0 | 0 / 35 | |
| 1.5.0 | 0 / 35 | |
| 1.4.0 | 0 / 35 | |
| 1.3.0 | 0 / 35 | |
| 1.2.0 | 0 / 35 | |
| 1.1.0 | 0 / 35 | |
| 1.0.0 | 0 / 35 |
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.