← Home

bytes

npm Repository Homepage

Utility to parse a string bytes to bytes and vice-versa

18
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

tjholowaychukdougwilson

Keywords

bytebytesutilityparseparserconvertconverter

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Well-known legitimate transition from tjholowaychuk to dougwilson across the Express ecosystem. ai
maintainer-change maintainer-added AI (maintainer-change): dougwilson is the established maintainer of bytes and many related Express packages. ai
source-diff source-size-tripled AI (source-diff): Growth from ~1KB to ~3KB is trivial for a utility package adding features; not indicative of payload injection. ai
semgrep semgrep:dynamic-require AI (semgrep): The dynamic requires load local lib files via __dirname + static path strings — not user-controlled input. This is a benign local module loading pattern stable for this package. ai

Versions (showing 18 of 18)

Version Deps Published
3.1.2 0 / 4
3.1.1 0 / 4
3.1.0 0 / 3
3.0.0 0 / 2
2.5.0 0 / 2
2.4.0 0 / 1
2.3.0 0 / 1
2.2.0 0 / 1
2.1.0 0 / 1
2.0.2 0 / 1
2.0.1 0 / 2
2.0.0 1 / 2
1.0.0 0 / 2
0.3.0 0 / 2
0.2.1 0 / 2
0.2.0 0 / 2
0.1.0 0 / 2
0.0.1 0 / 2

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v2.5.0

1 finding
LOW No provenance attestation provenance

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

v2.4.0

1 finding
LOW No provenance attestation provenance

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

v2.3.0

1 finding
LOW No provenance attestation provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

2 findings
HIGH Publisher changed: tjholowaychuk → dougwilson (on 2015-05-08) provenance

This version was published by a different npm account than previous versions on 2015-05-08. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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