stringz
Zero-dependency unicode-aware string tools
12
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
sallar
Keywords
stringtruncatelengthunicodesubstrsubstringemojipadleftpadrightpadlengthcount
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Package is 3555 days old; lack of Sigstore provenance is expected for this era and is not a security concern for this established package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 1 / 10 | |
| 2.0.0 | 1 / 10 | |
| 1.0.0 | 1 / 11 | |
| 0.4.0 | 0 / 11 | |
| 0.3.0 | 0 / 13 | |
| 0.2.3 | 0 / 13 | |
| 0.2.2 | 0 / 13 | |
| 0.2.1 | 0 / 13 | |
| 0.2.0 | 0 / 13 | |
| 0.1.2 | 0 / 7 | |
| 0.1.1 | 0 / 7 | |
| 0.1.0 | 0 / 7 |
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.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.