split-if-boxed-bug-x — Greenflagged

Tests if a value is a string with the boxed bug; splits to an array.

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

xotic750

Keywords

utilityboxed-stringsplitbugmodulejavascriptnodejsbrowser

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file:dist/split-if-boxed-bug-x.js	AI (source-diff): False positive: file is standard webpack UMD bundle. 'Network' pattern is UMD env detection; 'exec' is Function('return this')() global accessor idiom, not malicious.	ai	2026/04/24
source-diff	net-exec-file:dist/split-if-boxed-bug-x.min.js	AI (source-diff): False positive: minified webpack UMD bundle. Same benign patterns as the non-minified dist file — UMD env checks and Function('return this')() global accessor.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Established package from trusted publisher with 159 approved packages; lack of Sigstore provenance is not a security risk for this package.	ai	2026/04/24

Versions (showing 30 of 30)

Version	Deps	Published
2.1.2	3 / 56	2019-08-28
2.1.1	3 / 56	2019-08-20
2.1.0	2 / 56	2019-08-14
2.0.23	2 / 53	2019-07-31
2.0.22	2 / 67	2019-07-27
2.0.21	2 / 67	2019-07-27
2.0.20	2 / 67	2019-07-26
2.0.19	2 / 67	2019-07-25
2.0.18	2 / 67	2019-07-24
2.0.17	2 / 67	2019-07-24
2.0.16	2 / 67	2019-07-24
2.0.15	2 / 67	2019-07-22
2.0.14	2 / 67	2019-07-21
2.0.13	2 / 66	2019-07-19
2.0.12	2 / 66	2019-07-18
2.0.11	2 / 66	2019-07-18
2.0.10	2 / 66	2019-07-17
2.0.9	2 / 66	2019-07-17
2.0.8	2 / 66	2019-07-17
2.0.7	2 / 66	2019-07-16
2.0.6	2 / 66	2019-07-16
2.0.5	2 / 66	2019-07-16
2.0.4	2 / 66	2019-07-15
2.0.3	2 / 66	2019-07-14
2.0.2	2 / 66	2019-07-13
2.0.1	2 / 66	2019-07-12
2.0.0	2 / 53	2019-07-10
1.1.1	2 / 28	2018-02-24
1.1.0	2 / 27	2017-09-27
1.0.0	2 / 27	2017-09-05

v2.1.2

1 finding

LOW No provenance attestation provenance

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

v2.1.1

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v2.0.22

1 finding

LOW No provenance attestation provenance

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

v2.0.21

1 finding

LOW No provenance attestation provenance

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

v2.0.20

1 finding

LOW No provenance attestation provenance

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

v2.0.19

1 finding

LOW No provenance attestation provenance

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

v2.0.18

1 finding

LOW No provenance attestation provenance

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

v2.0.17

1 finding

LOW No provenance attestation provenance

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

v2.0.16

1 finding

LOW No provenance attestation provenance

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

v2.0.15

1 finding

LOW No provenance attestation provenance

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

v2.0.14

1 finding

LOW No provenance attestation provenance

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

v2.0.13

1 finding

LOW No provenance attestation provenance

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

v2.0.12

1 finding

LOW No provenance attestation provenance

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

v2.0.11

1 finding

LOW No provenance attestation provenance

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

v2.0.10

1 finding

LOW No provenance attestation provenance

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

v2.0.9

1 finding

LOW No provenance attestation provenance

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

v2.0.8

1 finding

LOW No provenance attestation provenance

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

v2.0.7

1 finding

LOW No provenance attestation provenance

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

v2.0.6

1 finding

LOW No provenance attestation provenance

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

v2.0.5

1 finding

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

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

3 findings

HIGH New file with network + code execution: dist/split-if-boxed-bug-x.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: dist/split-if-boxed-bug-x.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

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

INFO No provenance attestation provenance

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

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

v1.0.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.