react-split-pane — Greenflagged

React split-pane component with hooks and TypeScript

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

tomkpwuweiweiwu

Keywords

reactreact-componentsplit-panereact-split-panetypescripthooksresizablepaneslayoutaccessibility

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/index.cjs	AI (source-diff): Standard Rollup/terser minified output of a React split-pane component. Readable structure, no suspicious patterns.	ai	2026/04/23
source-diff	obfuscated-file:dist/index.js	AI (source-diff): Standard Rollup/terser minified ESM output of a React split-pane component. Readable structure, no suspicious patterns.	ai	2026/04/23
provenance	publisher-changed	AI (provenance): Publisher changed back to tomkp, the original author (account age matches package age). Legitimate reclaim.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): wuweiweiwu was a previous co-maintainer; adding them back is consistent with project history.	ai	2026/04/23

Versions (showing 51 of 97)

View all versions

Version	Deps	Published
3.2.0	0 / 24	2026-02-19
3.1.0	0 / 24	2026-02-18
3.0.6	0 / 24	2026-01-15
3.0.5	0 / 24	2026-01-12
3.0.4	0 / 24	2025-12-24
3.0.2	0 / 24	2025-12-22
3.0.1	0 / 24	2025-12-22
3.0.0	0 / 24	2025-12-22
2.0.3	8 / 25	2019-12-23
2.0.2	8 / 25	2018-05-17
2.0.0	8 / 24	2018-03-10
0.1.92	3 / 43	2020-08-10
0.1.91	3 / 39	2020-03-23
0.1.89	3 / 38	2019-11-12
0.1.87	3 / 32	2019-03-20
0.1.86	3 / 32	2019-03-20
0.1.85	5 / 30	2018-12-10
0.1.84	4 / 36	2018-09-10
0.1.83	4 / 36	2018-09-08
0.1.82	4 / 36	2018-07-11
0.1.81	4 / 40	2018-06-29
0.1.77	3 / 22	2018-02-11
0.1.76	5 / 19	2018-02-01
0.1.75	5 / 19	2018-02-01
0.1.74	5 / 19	2017-12-21
0.1.72	6 / 19	2017-12-20
0.1.71	5 / 19	2017-11-15
0.1.70	5 / 19	2017-11-12
0.1.69	5 / 19	2017-11-12
0.1.68	5 / 19	2017-10-25
0.1.67	5 / 18	2017-10-25
0.1.66	3 / 17	2017-08-14
0.1.65	3 / 23	2017-07-13
0.1.64	3 / 23	2017-07-08
0.1.63	3 / 24	2017-04-17
0.1.62	3 / 25	2017-04-16
0.1.61	2 / 25	2017-03-23
0.1.60	2 / 25	2017-03-23
0.1.59	2 / 25	2017-03-07
0.1.58	2 / 25	2017-02-28
0.1.57	2 / 25	2016-11-30
0.1.56	2 / 25	2016-11-25
0.1.55	2 / 25	2016-11-19
0.1.54	2 / 25	2016-11-17
0.1.53	2 / 25	2016-11-17
0.1.52	2 / 25	2016-10-31
0.1.51	2 / 25	2016-10-13
0.1.50	1 / 25	2016-10-09
0.1.49	1 / 25	2016-10-07
0.1.48	0 / 26	2016-10-06
0.1.47	0 / 25	2016-10-05

v3.2.0

1 finding

LOW No provenance attestation provenance

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

v3.1.0

1 finding

LOW No provenance attestation provenance

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

v3.0.6

1 finding

LOW No provenance attestation provenance

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

v3.0.5

1 finding

LOW No provenance attestation provenance

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

v3.0.4

1 finding

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.0.1

4 findings

HIGH Publisher changed: wuweiweiwu → tomkp (on 2025-12-22) provenance

This version was published by a different npm account than previous versions on 2025-12-22. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/index.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v3.0.0

4 findings

HIGH Publisher changed: wuweiweiwu → tomkp (on 2025-12-22) provenance

This version was published by a different npm account than previous versions on 2025-12-22. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/index.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

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

1 finding

LOW No provenance attestation provenance

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