← Home

split-string

Easy way to split a string on a given character unless it's quoted or escaped.

19
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

doowbjonschlinkert

Keywords

characterescapesplitstring

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): doowb (Brian Woodward) is a listed contributor and long-time collaborator of jonschlinkert; this is a known legitimate maintainer transition. ai
publish-pattern dormant-publish AI (publish-pattern): Mature utility package with infrequent updates; 251-day gap is normal for stable libraries. ai
provenance no-provenance AI (provenance): Informational only; package predates provenance tooling and publisher is well-established. ai

Versions (showing 19 of 19)

Version Deps Published
6.1.0 0 / 4
6.0.0 0 / 3
5.0.4 2 / 3
5.0.3 2 / 3
5.0.2 2 / 3
5.0.1 2 / 3
5.0.0 2 / 3
4.0.0 1 / 2
3.1.0 1 / 2
3.0.2 1 / 4
3.0.1 1 / 4
3.0.0 1 / 4
2.1.1 1 / 4
2.1.0 1 / 4
2.0.0 1 / 2
1.0.1 1 / 2
1.0.0 1 / 2
0.1.1 1 / 1
0.1.0 1 / 1

v6.1.0

2 findings
HIGH Publisher changed: jonschlinkert → doowb (on 2019-04-22) provenance

This version was published by a different npm account than previous versions on 2019-04-22. 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.

v6.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.

v5.0.4

1 finding
INFO No provenance attestation provenance

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

v5.0.3

1 finding
INFO No provenance attestation provenance

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

v5.0.2

1 finding
INFO No provenance attestation provenance

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

v5.0.1

1 finding
INFO No provenance attestation provenance

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

v5.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.