← Home

runes

npm Repository Homepage

Unicode-aware JS string splitting

8
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

dotcypress

Keywords

unicodeemojirunessplitsplit string

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): runes is a legitimate, long-established package (84k weekly downloads, ~10 years old). Version 0.0.0 is its genuine historical initial release, not a malicious throwaway. ai
bogus-package bogus-package AI (bogus-package): Signals reflect an early bootstrap version from ~2015 before the package was fully developed. The package is legitimate with 84k weekly downloads and a trusted publisher. ai

Versions (showing 8 of 8)

Version Deps Published
0.4.3 0 / 8
0.4.2 0 / 8
0.4.1 0 / 8
0.4.0 0 / 7
0.3.0 0 / 7
0.2.0 0 / 7
0.1.0 0 / 7
0.0.0 0 / 0

v0.4.3

1 finding
LOW No provenance attestation provenance

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

v0.4.2

1 finding
LOW No provenance attestation provenance

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

v0.4.1

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

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