rc-virtual-list
React Virtual List Component
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): rc-virtual-list is a long-established package (2482 days, 142 versions) from a trusted publisher in the react-component org. Version 0.0.0 is a known placeholder pattern for this ecosystem, not a malicious signal. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 2481-day history and trusted publisher; lack of Sigstore provenance is common and not a security concern here. | ai |
Versions (showing 5 of 105)
| Version | Deps | Published |
|---|---|---|
| 1.1.0 | 2 / 14 | |
| 1.0.1 | 2 / 14 | |
| 1.0.0 | 2 / 13 | |
| 0.0.1 | 2 / 13 | |
| 0.0.0 | 2 / 13 |
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.