@fluentui/react-table
React components for building web experiences
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@griffel/react | AI (dependencies): Griffel is Microsoft's CSS-in-JS library, a first-party dependency of the Fluent UI ecosystem. Stable and expected for this package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-aria | AI (dependencies): First-party Fluent UI sibling package from the microsoft/fluentui monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-icons | AI (dependencies): First-party Fluent UI sibling package from the microsoft/fluentui monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-radio | AI (dependencies): First-party Fluent UI sibling package from the microsoft/fluentui monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party Fluent UI sibling package from the microsoft/fluentui monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-avatar | AI (dependencies): First-party Fluent UI sibling package from the microsoft/fluentui monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/keyboard-keys | AI (dependencies): First-party Fluent UI sibling package from the microsoft/fluentui monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-tabster | AI (dependencies): First-party Fluent UI sibling package from the microsoft/fluentui monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-checkbox | AI (dependencies): First-party Fluent UI sibling package from the microsoft/fluentui monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party Fluent UI sibling package from the microsoft/fluentui monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): First-party Fluent UI sibling package from the microsoft/fluentui monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party Fluent UI sibling package from the microsoft/fluentui monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-context-selector | AI (dependencies): First-party Fluent UI sibling package from the microsoft/fluentui monorepo. Expected dependency. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft's Fluent UI monorepo does not currently publish with Sigstore provenance; this is consistent across all versions and not a security concern given the established publisher identity. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 9.19.16 | 14 / 0 | |
| 9.19.15 | 14 / 0 | |
| 9.19.14 | 14 / 0 | |
| 9.19.13 | 14 / 0 | |
| 9.19.12 | 14 / 0 | |
| 9.19.11 | 14 / 0 | |
| 9.19.10 | 14 / 0 | |
| 9.19.9 | 14 / 0 | |
| 9.19.8 | 14 / 0 | |
| 9.19.7 | 14 / 0 | |
| 9.19.6 | 14 / 6 | |
| 9.19.5 | 14 / 6 | |
| 9.19.4 | 14 / 6 | |
| 9.19.3 | 14 / 6 | |
| 9.19.2 | 14 / 6 | |
| 9.19.1 | 14 / 6 | |
| 9.19.0 | 14 / 6 | |
| 9.18.6 | 14 / 6 | |
| 9.18.5 | 14 / 6 | |
| 9.18.4 | 14 / 6 | |
| 9.18.3 | 14 / 6 | |
| 9.18.2 | 14 / 6 | |
| 9.18.1 | 14 / 6 | |
| 9.18.0 | 14 / 6 | |
| 9.17.7 | 14 / 6 | |
| 9.17.6 | 14 / 6 | |
| 9.17.5 | 14 / 6 | |
| 9.17.4 | 14 / 6 | |
| 9.17.3 | 14 / 6 | |
| 9.17.2 | 14 / 6 | |
| 9.17.1 | 14 / 6 | |
| 9.17.0 | 14 / 6 | |
| 9.16.9 | 14 / 6 | |
| 9.16.8 | 14 / 6 | |
| 9.16.7 | 14 / 6 |
v9.19.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.19.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.19.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.
v9.19.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.
v9.19.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.
v9.19.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.19.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.19.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.19.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.19.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.
v9.19.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.
v9.19.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.
v9.19.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.
v9.19.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.
v9.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.17.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.17.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.17.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.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.
v9.16.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.