@uxf/data-grid
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:react-data-grid | AI (dependencies): react-data-grid is a well-known open-source library; beta version pin is intentional and stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 424 versions; no provenance is consistent across all prior releases. | ai |
Versions (showing 55 of 55)
| Version | Deps | Published |
|---|---|---|
| 11.119.0 | 2 / 13 | |
| 11.118.2 | 2 / 13 | |
| 11.118.1 | 2 / 13 | |
| 11.118.0 | 2 / 13 | |
| 11.117.2 | 2 / 13 | |
| 11.115.0 | 2 / 13 | |
| 11.114.0 | 2 / 13 | |
| 11.113.0 | 2 / 13 | |
| 11.112.1 | 2 / 13 | |
| 11.112.0 | 2 / 13 | |
| 11.111.2 | 2 / 13 | |
| 11.111.0 | 2 / 13 | |
| 11.110.1 | 2 / 13 | |
| 11.110.0 | 2 / 13 | |
| 11.108.0 | 2 / 13 | |
| 11.107.0 | 8 / 10 | |
| 11.106.0 | 10 / 5 | |
| 11.105.0 | 10 / 5 | |
| 11.104.1 | 10 / 5 | |
| 11.104.0 | 10 / 5 | |
| 11.103.0 | 10 / 5 | |
| 11.102.0 | 10 / 5 | |
| 11.101.0 | 10 / 5 | |
| 11.100.1 | 10 / 5 | |
| 11.100.0 | 10 / 5 | |
| 11.99.1 | 10 / 5 | |
| 11.99.0 | 10 / 5 | |
| 11.97.0 | 10 / 5 | |
| 11.96.1 | 10 / 5 | |
| 11.95.2 | 10 / 5 | |
| 11.95.1 | 10 / 5 | |
| 11.95.0 | 10 / 5 | |
| 11.94.0 | 10 / 5 | |
| 11.93.3 | 10 / 5 | |
| 11.93.2 | 10 / 5 | |
| 11.93.1 | 10 / 5 | |
| 11.93.0 | 10 / 5 | |
| 11.92.3 | 8 / 5 | |
| 11.92.2 | 8 / 5 | |
| 11.92.1 | 8 / 5 | |
| 11.92.0 | 8 / 5 | |
| 11.91.0 | 8 / 5 | |
| 11.89.0 | 9 / 5 | |
| 11.88.2 | 9 / 5 | |
| 11.88.1 | 9 / 5 | |
| 11.88.0 | 9 / 5 | |
| 11.86.0 | 9 / 5 | |
| 11.80.4 | 9 / 5 | |
| 11.74.5 | 9 / 5 | |
| 11.74.4 | 9 / 5 | |
| 11.72.3 | 9 / 5 | |
| 11.70.0 | 9 / 5 | |
| 11.67.0 | 9 / 5 | |
| 11.64.5 | 9 / 5 | |
| 11.63.1 | 9 / 5 |
v11.119.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.118.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.118.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.118.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.117.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.115.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.114.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.108.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.107.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.106.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.105.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.104.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.104.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.103.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.102.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.101.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.100.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.100.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.99.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.99.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.97.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.96.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.95.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.95.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.95.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.94.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.93.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.93.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.93.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.92.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.92.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.92.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.92.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.91.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.89.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.88.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.88.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.88.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.86.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.
v11.80.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.
v11.74.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.
v11.74.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.
v11.72.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.
v11.70.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.
v11.67.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.
v11.64.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.
v11.63.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.