rc-table
table ui component for react
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:browserify-jsx | AI (dependencies): browserify-jsx is a build-time JSX transform tool used in browserify config only; not a runtime dependency with security implications for consumers of rc-table. | ai | |
| phantom-deps | phantom-dep:rc-util | AI (phantom-deps): rc-util is a legitimate dependency used transitively in rc-table; phantom-dep warnings are expected for this package type. | ai | |
| phantom-deps | phantom-dep:shallowequal | AI (phantom-deps): shallowequal is a legitimate dependency used transitively; phantom-dep warnings are expected for this package type. | ai | |
| phantom-deps | phantom-dep:lodash.get | AI (phantom-deps): lodash.get is a legitimate dependency used transitively; phantom-dep warnings are expected for this package type. | ai | |
| phantom-deps | phantom-dep:warning | AI (phantom-deps): warning is a legitimate dependency used transitively; phantom-dep warnings are expected for this package type. | ai | |
| phantom-deps | phantom-dep:mini-store | AI (phantom-deps): mini-store is properly declared in dependencies; phantom-dep on stable packages is a false positive. | ai | |
| phantom-deps | phantom-dep:react-lifecycles-compat | AI (phantom-deps): react-lifecycles-compat is properly declared in dependencies; phantom-dep on stable packages is a false positive. | ai | |
| phantom-deps | phantom-dep:component-classes | AI (phantom-deps): component-classes is properly declared in dependencies; phantom-dep on stable packages is a false positive. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): prop-types is properly declared in dependencies; phantom-dep on stable packages is a false positive. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Lodash is properly declared in dependencies and used indirectly; phantom-dep on stable packages is a false positive. | ai | |
| source-diff | net-exec-file:dist/rc-table.min.js | AI (source-diff): Minified webpack UMD bundle; same false positive pattern as the non-minified dist file. Stable for this package. | ai | |
| source-diff | net-exec-file:dist/rc-table.js | AI (source-diff): Standard webpack UMD bundle for a React component library; call() and network patterns are from webpack runtime and bundled deps, not malicious. | ai | |
| source-diff | large-new-source-files | AI (source-diff): rc-table grew from v3.x to v7.x; large file count increase reflects years of legitimate feature development, not injected code. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps (classnames, rc-util, rc-virtual-list, rc-resize-observer, @babel/runtime, @rc-component/context) are legitimate react-component ecosystem packages. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from 9KB to 385KB reflects major version evolution (v3→v7) with TypeScript, virtual list, and other features added over years. | ai | |
| provenance | publisher-changed | AI (provenance): yiminghe is a known Alibaba/Ant Design contributor and co-maintainer in the same react-component org; transition from dxq613 is a legitimate handoff within the same organization. | ai | |
| provenance | no-provenance | AI (provenance): Package was published in 2015, well before Sigstore provenance was available; no-provenance is expected for this era. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): yiminghe is a long-standing ecosystem contributor (first seen ~4157 days ago) and is listed as a co-maintainer in package.json; addition is legitimate. | ai | |
| phantom-deps | phantom-dep:browserify-shim | AI (phantom-deps): browserify-shim is declared in dependencies and referenced in browserify-shim config — not a phantom dep, just an indirect usage pattern. | ai | |
| phantom-deps | phantom-dep:browserify-jsx | AI (phantom-deps): browserify-jsx is declared in dependencies and referenced in browserify transform config — not a phantom dep, just an indirect usage pattern. | ai | |
| install-scripts | install-script:install | AI (install-scripts): Install script runs 'gulp config', a standard build configuration step in this package's documented workflow. No network fetching or malicious behavior. | ai | |
| semgrep | semgrep:child-process-exec | AI (semgrep): cp.exec in gulpfile.js runs git commands for release tagging — standard dev tooling, not reachable at install or runtime. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used only in gulpfile.js for dev tooling (git tagging). Not reachable during normal install or runtime. | ai |
Versions (showing 100 of 414)
| Version | Deps | Published |
|---|---|---|
| 7.21.1 | 5 / 35 | |
| 7.21.0 | 5 / 35 | |
| 7.20.5 | 5 / 34 | |
| 7.20.4 | 5 / 34 | |
| 7.20.3 | 5 / 34 | |
| 7.20.2 | 5 / 34 | |
| 7.20.1 | 5 / 34 | |
| 7.20.0 | 5 / 34 | |
| 7.19.2 | 5 / 35 | |
| 7.19.1 | 5 / 35 | |
| 7.19.0 | 5 / 35 | |
| 7.18.1 | 5 / 35 | |
| 7.18.0 | 5 / 35 | |
| 7.17.2 | 5 / 35 | |
| 7.17.1 | 5 / 35 | |
| 7.17.0 | 5 / 35 | |
| 7.16.3 | 5 / 35 | |
| 7.16.2 | 5 / 35 | |
| 7.16.1 | 5 / 35 | |
| 7.16.0 | 5 / 35 | |
| 7.15.2 | 5 / 35 | |
| 7.15.1 | 5 / 35 | |
| 7.15.0 | 5 / 35 | |
| 7.14.1 | 5 / 35 | |
| 7.14.0 | 5 / 35 | |
| 7.13.3 | 5 / 35 | |
| 7.13.2 | 5 / 35 | |
| 7.13.1 | 5 / 35 | |
| 7.13.0 | 5 / 35 | |
| 7.12.5 | 5 / 35 | |
| 7.12.4 | 5 / 35 | |
| 7.12.3 | 5 / 35 | |
| 7.12.2 | 5 / 35 | |
| 7.12.1 | 5 / 35 | |
| 7.12.0 | 5 / 35 | |
| 7.11.3 | 5 / 31 | |
| 7.11.2 | 5 / 31 | |
| 7.11.1 | 5 / 31 | |
| 7.11.0 | 5 / 31 | |
| 7.10.4 | 5 / 31 | |
| 7.10.3 | 5 / 31 | |
| 7.10.2 | 5 / 31 | |
| 7.10.1 | 6 / 30 | |
| 7.10.0 | 6 / 30 | |
| 7.9.10 | 6 / 30 | |
| 7.9.9 | 6 / 30 | |
| 7.9.8 | 6 / 30 | |
| 7.9.7 | 6 / 30 | |
| 7.9.6 | 6 / 30 | |
| 7.9.5 | 6 / 30 | |
| 7.9.4 | 6 / 30 | |
| 7.9.3 | 6 / 30 | |
| 7.9.2 | 6 / 30 | |
| 7.9.1 | 6 / 30 | |
| 7.9.0 | 6 / 30 | |
| 7.8.6 | 6 / 30 | |
| 7.8.5 | 6 / 30 | |
| 7.8.4 | 6 / 30 | |
| 7.8.3 | 6 / 30 | |
| 7.8.2 | 6 / 30 | |
| 7.8.1 | 6 / 30 | |
| 7.8.0 | 6 / 30 | |
| 7.7.2 | 6 / 30 | |
| 7.7.1 | 5 / 29 | |
| 7.7.0 | 5 / 28 | |
| 7.6.7 | 5 / 27 | |
| 7.6.6 | 5 / 27 | |
| 7.6.4 | 9 / 27 | |
| 7.6.3 | 9 / 27 | |
| 7.6.2 | 9 / 27 | |
| 7.6.1 | 9 / 27 | |
| 7.6.0 | 9 / 27 | |
| 7.5.10 | 5 / 28 | |
| 7.5.9 | 5 / 27 | |
| 7.5.8 | 5 / 27 | |
| 7.5.7 | 9 / 27 | |
| 7.5.6 | 9 / 27 | |
| 7.5.5 | 9 / 27 | |
| 7.5.4 | 9 / 27 | |
| 7.5.3 | 9 / 27 | |
| 7.5.2 | 9 / 27 | |
| 7.5.1 | 9 / 27 | |
| 7.5.0 | 9 / 27 | |
| 7.4.5 | 9 / 27 | |
| 7.4.4 | 9 / 27 | |
| 7.4.3 | 9 / 27 | |
| 7.4.2 | 9 / 27 | |
| 7.4.1 | 9 / 27 | |
| 7.4.0 | 9 / 27 | |
| 7.3.14 | 10 / 27 | |
| 7.3.13 | 10 / 27 | |
| 7.3.12 | 10 / 27 | |
| 7.3.11 | 10 / 27 | |
| 7.3.10 | 10 / 27 | |
| 7.3.9 | 10 / 27 | |
| 7.3.8 | 10 / 27 | |
| 7.3.7 | 10 / 27 | |
| 7.3.6 | 10 / 27 | |
| 7.3.5 | 10 / 27 | |
| 7.3.4 | 10 / 27 |
v7.21.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.
v7.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.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.
v7.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.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.
v7.19.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.
v7.18.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.
v7.18.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-09-15. This could indicate a legitimate maintainer transition or an account compromise.
v7.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.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.
v7.17.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.
v7.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.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.
v7.16.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.
v7.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.15.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.
v7.15.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.
v7.14.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.
v7.14.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.
v7.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.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.
v7.13.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.
v7.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.12.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.
v7.12.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.
v7.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.11.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.
v7.11.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.
v7.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.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.
v7.10.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.
v7.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.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.
v7.9.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.
v7.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-07-22. This could indicate a legitimate maintainer transition or an account compromise.
v7.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.8.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.
v7.8.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.
v7.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.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.
v7.7.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.
v7.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.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.
v7.6.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.
v7.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.8
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-05-07. This could indicate a legitimate maintainer transition or an account compromise.
v7.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.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.
v7.5.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.
v7.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.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.
v7.4.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.
v7.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.13
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-03-26. This could indicate a legitimate maintainer transition or an account compromise.
v7.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.