@tanstack/react-table
Headless UI for building powerful tables & datagrids for React.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish-env metadata change on a trusted first-party package; not a risk signal. | ai | |
| dependencies | unvetted-dep:@tanstack/table-core | AI (dependencies): @tanstack/table-core is the first-party TanStack core package, a standard monorepo dependency of @tanstack/react-table. Not a risk. | ai |
Versions (showing 51 of 118)
| Version | Deps | Published |
|---|---|---|
| 8.21.3 | 1 / 2 | |
| 8.21.2 | 1 / 2 | |
| 8.20.6 | 1 / 2 | |
| 8.20.5 | 1 / 2 | |
| 8.20.1 | 1 / 2 | |
| 8.19.4 | 1 / 2 | |
| 8.19.3 | 1 / 2 | |
| 8.19.2 | 1 / 2 | |
| 8.19.1 | 1 / 2 | |
| 8.17.3 | 1 / 2 | |
| 8.17.0 | 1 / 2 | |
| 8.16.0 | 1 / 2 | |
| 8.15.3 | 1 / 2 | |
| 8.15.2 | 1 / 2 | |
| 8.15.1 | 1 / 2 | |
| 8.15.0 | 1 / 2 | |
| 8.14.0 | 1 / 2 | |
| 8.13.2 | 1 / 2 | |
| 8.13.1 | 1 / 2 | |
| 8.13.0 | 1 / 2 | |
| 8.12.0 | 1 / 4 | |
| 8.11.8 | 1 / 4 | |
| 8.11.7 | 1 / 4 | |
| 8.11.6 | 1 / 4 | |
| 8.11.5 | 1 / 4 | |
| 8.11.4 | 1 / 4 | |
| 8.11.3 | 1 / 4 | |
| 8.11.2 | 1 / 0 | |
| 8.11.1 | 1 / 0 | |
| 8.11.0 | 1 / 0 | |
| 8.10.7 | 1 / 0 | |
| 8.10.6 | 1 / 0 | |
| 8.10.5 | 1 / 0 | |
| 8.10.4 | 1 / 0 | |
| 8.10.3 | 1 / 0 | |
| 8.10.2 | 1 / 0 | |
| 8.10.1 | 1 / 0 | |
| 8.10.0 | 1 / 0 | |
| 8.9.11 | 1 / 0 | |
| 8.9.10 | 1 / 0 | |
| 8.9.9 | 1 / 0 | |
| 8.9.8 | 1 / 0 | |
| 8.9.7 | 1 / 0 | |
| 8.9.3 | 1 / 0 | |
| 8.9.2 | 1 / 0 | |
| 8.9.1 | 1 / 0 | |
| 8.9.0 | 1 / 0 | |
| 8.8.5 | 1 / 0 | |
| 8.8.4 | 1 / 0 | |
| 8.8.2 | 1 / 0 | |
| 8.8.1 | 1 / 0 |
v8.16.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.15.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.15.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.15.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.15.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.14.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.13.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.13.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.13.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tannerlinsley.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.