← Home

utf8-binary-cutter

truncate UTF-8 strings to a given binary size

5
Versions
public domain
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

jbustinlemondeoffirmo

Keywords

utf-8truncate

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from offirmo to lemonde reflects a legitimate org transfer; repo URL, author email (@lemonde.fr), and publisher track record all confirm the Le Monde organization owns this package. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers jbustin and lemonde are consistent with the Le Monde org transfer; corroborated by repo URL and author email domain. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by publish is explained by the organizational transfer to Le Monde; no code changes or suspicious scripts were introduced. ai

Versions (showing 5 of 5)

Version Deps Published
0.9.2 1 / 4
0.9.1 1 / 4
0.9.0 1 / 4
0.8.1 1 / 4
0.8.0 1 / 5

v0.9.2

2 findings
HIGH Publisher changed: offirmo → lemonde (on 2018-06-15) provenance

This version was published by a different npm account than previous versions on 2018-06-15. 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.

v0.9.1

1 finding
LOW No provenance attestation provenance

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

v0.9.0

1 finding
LOW No provenance attestation provenance

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

v0.8.1

1 finding
LOW No provenance attestation provenance

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

v0.8.0

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.