react-virtualized — Greenflagged

React components for efficiently rendering large, scrollable lists and tabular data

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

yamadapctrysoundbrianvaughnwuweiweiwushhnjk

Keywords

reactreactjsreact-componentvirtuallistscrollinginfinitevirtualizedtablefixedheaderflexflexboxgridspreadsheet

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): The publisher change (trysound → brianvaughn) occurred in 2018 and reflects the canonical author Brian Vaughn taking over his own package. This is a stable historical fact, not a security concern.	ai	2026/04/24
source-diff	net-exec-file:dist/commonjs/vendor/binarySearchBounds.js	AI (source-diff): Inlined copy of open-source binary-search-bounds library for CSP compliance; pure algorithmic code with no network calls or malicious execution.	ai	2026/04/24
source-diff	net-exec-file:dist/commonjs/vendor/intervalTree.js	AI (source-diff): Inlined copy of open-source interval-tree-1d library for CSP compliance; pure data structure code with no network calls or malicious execution.	ai	2026/04/24
source-diff	net-exec-file:dist/es/vendor/binarySearchBounds.js	AI (source-diff): ES module variant of inlined binary-search-bounds; same rationale as commonjs variant — CSP fix, no malicious behavior.	ai	2026/04/24
source-diff	net-exec-file:dist/es/vendor/intervalTree.js	AI (source-diff): ES module variant of inlined interval-tree-1d; same rationale as commonjs variant — CSP fix, no malicious behavior.	ai	2026/04/24
phantom-deps	phantom-dep:loose-envify	AI (phantom-deps): loose-envify is legitimately used as a browserify transform (declared in package.json browserify config); not a phantom dep for this package.	ai	2026/04/24

Versions (showing 51 of 259)

View all versions

Version	Deps	Published
9.22.6	6 / 67	2025-01-20
9.22.5	6 / 66	2023-04-17
9.22.4	6 / 66	2023-04-09
9.22.2	6 / 66	2020-08-10
9.22.1	6 / 66	2020-08-10
9.22.0	6 / 66	2020-08-10
9.21.2	6 / 64	2019-11-12
9.21.1	7 / 63	2019-05-08
9.21.0	6 / 63	2018-10-23
9.20.1	6 / 63	2018-07-11
9.20.0	6 / 63	2018-06-25
9.19.1	6 / 62	2018-05-23
9.19.0	6 / 62	2018-05-16
9.18.5	5 / 61	2018-01-31
9.18.4	5 / 61	2018-01-31
9.18.3	5 / 61	2018-01-31
9.18.2	5 / 61	2018-01-31
9.18.1	5 / 61	2018-01-31
9.18.0	5 / 61	2018-01-21
9.17.3	5 / 61	2018-01-16
9.17.2	5 / 61	2018-01-15
9.17.1	5 / 61	2018-01-14
9.17.0	5 / 61	2018-01-13
9.16.1	5 / 61	2018-01-06
9.16.0	5 / 61	2018-01-05
9.15.0	5 / 61	2017-12-31
9.14.1	5 / 61	2017-12-18
9.14.0	5 / 61	2017-12-17
9.13.0	5 / 61	2017-11-25
9.12.0	5 / 61	2017-10-21
9.11.1	5 / 61	2017-10-15
9.11.0	5 / 58	2017-10-14
9.10.1	5 / 58	2017-09-18
9.10.0	5 / 58	2017-09-18
9.9.0	5 / 50	2017-07-09
9.8.0	5 / 50	2017-06-13
9.7.6	5 / 50	2017-05-20
9.7.5	5 / 50	2017-05-08
9.7.4	5 / 50	2017-04-29
9.7.3	5 / 51	2017-04-12
9.7.2	5 / 51	2017-04-09
9.7.1	5 / 50	2017-04-09
9.7.0	4 / 50	2017-04-06
9.6.1	4 / 50	2017-04-05
9.6.0	4 / 50	2017-04-05
9.5.0	5 / 50	2017-04-03
9.4.2	5 / 50	2017-04-02
9.4.1	5 / 50	2017-03-31
9.4.0	5 / 50	2017-03-27
9.3.0	4 / 50	2017-03-15
9.2.3	4 / 50	2017-03-14

v9.22.6

1 finding

LOW No provenance attestation provenance

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

v9.22.5

1 finding

LOW No provenance attestation provenance

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

v9.22.4

2 findings

HIGH Publisher changed: shhnjk → brianvaughn (on 2023-04-09) provenance

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

v9.22.2

1 finding

LOW No provenance attestation provenance

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

v9.22.1

1 finding

LOW No provenance attestation provenance

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

v9.22.0

1 finding

LOW No provenance attestation provenance

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

v9.21.2

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wuweiweiwu.

LOW No provenance attestation provenance

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

v9.21.1

1 finding

LOW No provenance attestation provenance

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

v9.21.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wuweiweiwu.

LOW No provenance attestation provenance

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

v9.20.1

1 finding

LOW No provenance attestation provenance

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

v9.20.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wuweiweiwu.

LOW No provenance attestation provenance

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

v9.19.1

1 finding

LOW No provenance attestation provenance

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

v9.19.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: trysound → wuweiweiwu (on 2018-05-16) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-05-16. This could indicate a legitimate maintainer transition or an account compromise.

v9.18.5

1 finding

LOW No provenance attestation provenance

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

v9.18.4

1 finding

LOW No provenance attestation provenance

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

v9.18.3

1 finding

LOW No provenance attestation provenance

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

v9.18.2

1 finding

LOW No provenance attestation provenance

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

v9.18.1

1 finding

LOW No provenance attestation provenance

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

v9.18.0

2 findings

HIGH Publisher changed: trysound → brianvaughn (on 2018-01-21) provenance

This version was published by a different npm account than previous versions on 2018-01-21. 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.

v9.17.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: brianvaughn → trysound (on 2018-01-16) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-01-16. This could indicate a legitimate maintainer transition or an account compromise.

v9.17.2

1 finding

LOW No provenance attestation provenance

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

v9.17.1

1 finding

LOW No provenance attestation provenance

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

v9.17.0

2 findings

HIGH Publisher changed: trysound → brianvaughn (on 2018-01-13) provenance

This version was published by a different npm account than previous versions on 2018-01-13. 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.

v9.16.1

2 findings

HIGH Publisher changed: brianvaughn → trysound (on 2018-01-06) provenance

This version was published by a different npm account than previous versions on 2018-01-06. 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.

v9.16.0

2 findings

HIGH Publisher changed: brianvaughn → trysound (on 2018-01-05) provenance

This version was published by a different npm account than previous versions on 2018-01-05. 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.

v9.15.0

1 finding

LOW No provenance attestation provenance

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

v9.14.1

1 finding

LOW No provenance attestation provenance

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

v9.14.0

1 finding

LOW No provenance attestation provenance

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

v9.13.0

1 finding

LOW No provenance attestation provenance

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

v9.12.0

1 finding

LOW No provenance attestation provenance

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

v9.11.1

1 finding

LOW No provenance attestation provenance

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

v9.11.0

1 finding

LOW No provenance attestation provenance

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

v9.10.1

1 finding

LOW No provenance attestation provenance

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

v9.10.0

1 finding

LOW No provenance attestation provenance

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

v9.9.0

1 finding

LOW No provenance attestation provenance

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

v9.8.0

1 finding

LOW No provenance attestation provenance

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

v9.7.6

1 finding

LOW No provenance attestation provenance

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

v9.7.5

1 finding

LOW No provenance attestation provenance

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

v9.7.4

1 finding

LOW No provenance attestation provenance

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

v9.7.3

1 finding

LOW No provenance attestation provenance

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

v9.7.2

1 finding

LOW No provenance attestation provenance

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

v9.7.1

1 finding

LOW No provenance attestation provenance

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

v9.7.0

1 finding

LOW No provenance attestation provenance

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

v9.6.1

1 finding

LOW No provenance attestation provenance

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

v9.6.0

5 findings

HIGH New file with network + code execution: dist/commonjs/vendor/binarySearchBounds.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/commonjs/vendor/intervalTree.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/es/vendor/binarySearchBounds.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/es/vendor/intervalTree.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.

v9.5.0

1 finding

LOW No provenance attestation provenance

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

v9.4.2

1 finding

LOW No provenance attestation provenance

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

v9.4.1

1 finding

LOW No provenance attestation provenance

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

v9.4.0

1 finding

LOW No provenance attestation provenance

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

v9.3.0

1 finding

LOW No provenance attestation provenance

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

v9.2.3

1 finding

LOW No provenance attestation provenance

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