@fluentui-react-native/tablist
A cross-platform TabList component using the Fluent Design System
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo component package from Microsoft's fluentui-react-native; short README and no keywords are typical for such packages and not indicative of spam. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft package published via trusted bot account; lack of Sigstore provenance is not a meaningful risk signal here. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/icon | AI (dependencies): Sibling package from the same Microsoft fluentui-react-native monorepo, published by the same trusted bot account. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/text | AI (dependencies): Sibling package from the same Microsoft fluentui-react-native monorepo, published by the same trusted bot account. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/framework | AI (dependencies): Sibling package from the same Microsoft fluentui-react-native monorepo, published by the same trusted bot account. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.8.3 | 9 / 22 | |
| 0.8.1 | 9 / 22 | |
| 0.8.0 | 9 / 22 | |
| 0.7.19 | 9 / 17 | |
| 0.7.18 | 9 / 17 | |
| 0.7.17 | 9 / 17 | |
| 0.7.16 | 9 / 17 | |
| 0.7.15 | 9 / 17 | |
| 0.7.14 | 9 / 17 | |
| 0.7.13 | 10 / 13 | |
| 0.7.12 | 10 / 13 | |
| 0.7.11 | 10 / 13 | |
| 0.7.10 | 10 / 13 | |
| 0.7.9 | 10 / 13 | |
| 0.7.8 | 10 / 13 | |
| 0.7.7 | 10 / 13 | |
| 0.7.6 | 10 / 13 | |
| 0.7.5 | 10 / 10 |
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.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.
v0.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.
v0.7.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.