@rc-component/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:@rc-component/util | AI (dependencies): Sibling package in the same @rc-component namespace from the react-component org; expected dependency for this package. | ai | |
| dependencies | unvetted-dep:@rc-component/context | AI (dependencies): Sibling package in the same @rc-component namespace from the react-component org; expected dependency for this package. | ai | |
| dependencies | unvetted-dep:@rc-component/virtual-list | AI (dependencies): Sibling package in the same @rc-component namespace from the react-component org; expected dependency for this package. | ai | |
| dependencies | unvetted-dep:@rc-component/resize-observer | AI (dependencies): Sibling package in the same @rc-component namespace from the react-component org; expected dependency for this package. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 1.10.2 | 5 / 38 | |
| 1.10.1 | 5 / 38 | |
| 1.10.0 | 5 / 38 | |
| 1.9.1 | 5 / 38 | |
| 1.9.0 | 5 / 38 | |
| 1.8.2 | 5 / 38 | |
| 1.8.1 | 5 / 41 | |
| 1.8.0 | 5 / 41 | |
| 1.7.0 | 5 / 39 | |
| 1.6.1 | 5 / 40 | |
| 1.6.0 | 5 / 40 | |
| 1.5.2 | 5 / 40 | |
| 1.5.0 | 5 / 40 | |
| 1.4.1 | 5 / 40 | |
| 1.4.0 | 5 / 40 | |
| 1.3.0 | 5 / 40 | |
| 1.2.7 | 5 / 40 | |
| 1.2.6 | 5 / 40 | |
| 1.2.5 | 5 / 40 | |
| 1.2.4 | 5 / 40 | |
| 1.2.3 | 5 / 40 | |
| 1.2.2 | 5 / 40 | |
| 1.2.1 | 5 / 40 | |
| 1.2.0 | 5 / 40 | |
| 1.1.1 | 5 / 45 | |
| 1.1.0 | 5 / 45 | |
| 1.0.2 | 5 / 45 | |
| 1.0.1 | 5 / 45 | |
| 1.0.0 | 5 / 45 |
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zombiej) than the most recent previously approved version (afc163) on 2025-11-22, but zombiej is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (afc163) than the most recent previously approved version (zombiej) on 2025-09-15, but afc163 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.7.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (afc163) than the most recent previously approved version (zombiej) on 2025-09-12, but afc163 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.6.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (afc163) than the most recent previously approved version (zombiej) on 2025-09-05, but afc163 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.6.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (afc163) than the most recent previously approved version (zombiej) on 2025-09-04, but afc163 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.5.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (afc163) than the most recent previously approved version (zombiej) on 2025-08-25, but afc163 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.