@libit/bufio
Buffer and serialization utilities for javascript
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:hex-decode | AI (semgrep): Buffer serialization library legitimately decodes hex strings as core functionality; this is not a malicious payload pattern. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Buffer serialization library legitimately decodes base64 strings as core functionality; this is not a malicious payload pattern. | ai | |
| provenance | no-provenance | AI (provenance): Absence of Sigstore provenance is common and not a security risk for this well-established package with a clean publisher history. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.4.2 | 1 / 4 | |
| 0.4.1 | 1 / 4 | |
| 0.3.0 | 1 / 4 | |
| 0.2.10 | 1 / 4 | |
| 0.2.9 | 1 / 4 | |
| 0.2.8 | 1 / 4 | |
| 0.2.7 | 1 / 4 | |
| 0.2.6 | 1 / 4 | |
| 0.2.5 | 1 / 4 | |
| 0.2.4 | 1 / 4 | |
| 0.2.3 | 1 / 4 | |
| 0.2.2 | 1 / 4 | |
| 0.2.1 | 1 / 4 | |
| 0.2.0 | 1 / 4 |
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.