← Home

@webbuf/rw

npm Repository Homepage

Read and write buffers, optimized with Rust/WASM for the web, node.js, deno, and bun.

19
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

ryanxcharles

Keywords

bufferbase64hexuint256int256uint128int128rustwasm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped @webbuf package; Levenshtein match to 'pg' is coincidental, not a typosquat. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped @webbuf package; Levenshtein match to 'qs' is coincidental, not a typosquat. ai

Versions (showing 19 of 19)

Version Deps Published
3.8.0 0 / 10
3.7.0 0 / 10
3.6.0 0 / 10
3.5.0 0 / 10
3.4.0 0 / 10
3.3.0 0 / 10
3.2.0 0 / 10
3.1.0 0 / 10
3.0.28 0 / 7
3.0.26 0 / 7
3.0.25 0 / 7
3.0.22 0 / 7
3.0.21 0 / 7
3.0.20 0 / 7
3.0.18 0 / 7
3.0.17 0 / 7
3.0.16 0 / 7
3.0.15 0 / 7
3.0.13 0 / 7

v3.0.26

1 finding
LOW No provenance attestation provenance

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

v3.0.25

1 finding
LOW No provenance attestation provenance

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

v3.0.22

1 finding
LOW No provenance attestation provenance

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

v3.0.21

1 finding
LOW No provenance attestation provenance

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

v3.0.20

1 finding
LOW No provenance attestation provenance

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

v3.0.18

1 finding
LOW No provenance attestation provenance

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

v3.0.17

1 finding
LOW No provenance attestation provenance

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

v3.0.16

1 finding
LOW No provenance attestation provenance

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

v3.0.15

1 finding
LOW No provenance attestation provenance

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

v3.0.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.