@atcute/util-text 0BSD 7 versions

@atcute/util-text

npm Repository Homepage

internal text utilities

7

Versions

0BSD

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

externdefs

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	bundled-binaries	AI (npm-metadata): Documented native grapheme segmentation prebuilds; loaded at runtime via standard prebuild pattern, not at install time.	ai	2026/05/05
semgrep	semgrep:dynamic-require	AI (semgrep): Pattern is a standard prebuilt native binding loader; stable for this package.	ai	2026/04/29

Versions (showing 7 of 7)

Version	Deps	Published
1.3.1	1 / 3	2026-04-19
1.3.0	1 / 3	2026-04-18
1.2.0	1 / 3	2026-03-18
1.1.1	1 / 0	2026-02-12
1.1.0	1 / 0	2026-01-30
1.0.0	1 / 0	2025-12-26
0.0.1	1 / 0	2025-12-26

v1.3.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.

v1.2.0

2 findings

HIGH Bundled binary files (6) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/darwin-arm64/grapheme.node • prebuilds/linux-arm64-glibc/grapheme.node • prebuilds/linux-arm64-musl/grapheme.node • prebuilds/linux-x64-glibc/grapheme.node • prebuilds/linux-x64-musl/grapheme.node • prebuilds/win32-x64/grapheme.node

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.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

LOW No provenance attestation provenance

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

v0.0.1

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.