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 |
|---|---|---|
| 5.6.5 | 7 / 15 | |
| 5.6.4 | 7 / 15 | |
| 5.6.3 | 7 / 15 | |
| 5.6.2 | 7 / 15 | |
| 5.6.1 | 7 / 15 | |
| 5.5.0 | 7 / 15 | |
| 5.4.2 | 7 / 15 | |
| 5.4.1 | 7 / 15 | |
| 5.4.0 | 7 / 15 | |
| 5.3.4 | 7 / 15 | |
| 5.3.3 | 7 / 15 | |
| 5.3.2 | 7 / 15 | |
| 5.3.1 | 6 / 15 | |
| 5.3.0 | 5 / 14 | |
| 5.2.15 | 5 / 14 | |
| 5.2.14 | 5 / 14 | |
| 5.2.13 | 5 / 14 | |
| 5.2.12 | 5 / 14 | |
| 5.2.11 | 5 / 14 | |
| 5.2.10 | 5 / 14 | |
| 5.2.9 | 5 / 14 | |
| 5.2.8 | 4 / 14 | |
| 5.2.7 | 4 / 10 | |
| 5.2.6 | 4 / 10 | |
| 5.2.5 | 4 / 10 | |
| 5.2.4 | 4 / 10 | |
| 5.2.3 | 4 / 10 | |
| 5.2.2 | 3 / 10 | |
| 5.2.1 | 3 / 10 | |
| 5.2.0 | 3 / 10 | |
| 5.1.2 | 3 / 10 | |
| 5.1.1 | 3 / 10 | |
| 5.1.0 | 3 / 10 | |
| 5.0.6 | 3 / 10 | |
| 5.0.5 | 3 / 10 | |
| 5.0.4 | 3 / 10 | |
| 5.0.3 | 3 / 10 | |
| 5.0.2 | 3 / 10 | |
| 5.0.1 | 3 / 10 | |
| 5.0.0 | 3 / 10 | |
| 4.6.0 | 3 / 10 | |
| 4.5.3 | 3 / 10 | |
| 4.5.2 | 3 / 10 | |
| 4.5.1 | 3 / 10 | |
| 4.5.0 | 3 / 10 | |
| 4.4.8 | 3 / 10 | |
| 4.4.7 | 3 / 10 | |
| 4.4.6 | 3 / 10 | |
| 4.4.5 | 3 / 10 | |
| 4.4.4 | 3 / 10 | |
| 4.4.3 | 3 / 10 | |
| 4.4.2 | 3 / 10 | |
| 4.4.1 | 3 / 10 | |
| 4.4.0 | 3 / 10 | |
| 4.3.9 | 3 / 10 | |
| 4.3.7 | 1 / 10 | |
| 4.3.6 | 1 / 10 | |
| 4.3.5 | 1 / 10 | |
| 4.3.4 | 1 / 10 | |
| 4.3.3 | 1 / 10 | |
| 4.3.2 | 1 / 10 | |
| 4.3.1 | 1 / 10 | |
| 4.3.0 | 1 / 10 | |
| 4.2.5 | 1 / 10 | |
| 4.2.4 | 1 / 10 | |
| 4.2.3 | 1 / 10 | |
| 4.2.2 | 1 / 10 | |
| 4.2.1 | 1 / 10 | |
| 4.2.0 | 1 / 10 | |
| 4.1.4 | 1 / 10 | |
| 4.1.3 | 1 / 10 | |
| 4.1.2 | 1 / 10 | |
| 4.1.1 | 1 / 10 | |
| 4.1.0 | 1 / 10 | |
| 4.0.6 | 1 / 10 | |
| 4.0.5 | 1 / 10 | |
| 4.0.4 | 1 / 10 | |
| 4.0.3 | 1 / 10 | |
| 4.0.2 | 1 / 10 | |
| 4.0.1 | 1 / 10 | |
| 4.0.0 | 1 / 10 | |
| 3.11.4 | 1 / 10 | |
| 3.11.3 | 1 / 10 | |
| 3.11.2 | 1 / 10 | |
| 3.11.1 | 1 / 10 | |
| 3.11.0 | 1 / 10 | |
| 3.10.1 | 1 / 10 | |
| 3.10.0 | 1 / 10 | |
| 3.9.4 | 1 / 10 | |
| 3.9.3 | 1 / 10 | |
| 3.9.2 | 1 / 10 | |
| 3.9.1 | 1 / 10 | |
| 3.9.0 | 1 / 10 | |
| 3.8.0 | 0 / 10 | |
| 3.7.1 | 0 / 10 | |
| 3.7.0 | 0 / 10 | |
| 3.6.3 | 0 / 10 | |
| 3.6.2 | 0 / 10 | |
| 3.6.1 | 0 / 10 | |
| 3.6.0 | 0 / 10 |
v5.6.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.3.3
4 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[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 2017-05-16. This could indicate a legitimate maintainer transition or an account compromise.
v5.3.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.
v5.3.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.
v5.3.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.
v5.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.14
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[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 2017-03-01. This could indicate a legitimate maintainer transition or an account compromise.
v5.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.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.
v5.2.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.
v5.2.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.
v5.2.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.
v5.2.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.
v5.2.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.
v5.2.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.
v5.2.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.
v5.2.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.
v5.2.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.
v5.2.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.
v5.2.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.
v5.2.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.
v5.1.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.
v5.1.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.
v5.1.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.
v5.0.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.
v5.0.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.
v5.0.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.
v5.0.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.
v5.0.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.
v5.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.
v5.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.
v4.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.
v4.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.
v4.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.
v4.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.
v4.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.
v4.4.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.
v4.4.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.
v4.4.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.
v4.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.
v4.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.
v4.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.
v4.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.
v4.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.
v4.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.
v4.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.
v4.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.
v4.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.
v4.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.
v4.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.
v4.3.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.
v4.3.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.
v4.3.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.
v4.3.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.
v4.2.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.
v4.2.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.
v4.2.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.
v4.2.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.
v4.2.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.
v4.2.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.
v4.1.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.
v4.1.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.
v4.1.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.
v4.1.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.
v4.1.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.
v4.0.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.
v4.0.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.
v4.0.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.
v4.0.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.
v4.0.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.
v4.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.
v4.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.
v3.11.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.