@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a first-party @fluentui-react-native sibling package, not third-party. | ai | |
| provenance | missing-githead | AI (provenance): Monorepo build tooling change, not a provenance regression for this trusted bot publisher. | 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 | |
| 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 | |
| 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 | |
| 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 | |
| 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 |
Versions (showing 51 of 92)
| Version | Deps | Published |
|---|---|---|
| 0.8.5 | 10 / 17 | |
| 0.8.4 | 9 / 18 | |
| 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 | |
| 0.7.4 | 10 / 8 | |
| 0.7.3 | 10 / 8 | |
| 0.7.2 | 10 / 8 | |
| 0.7.1 | 10 / 8 | |
| 0.7.0 | 10 / 8 | |
| 0.6.12 | 10 / 8 | |
| 0.6.11 | 10 / 8 | |
| 0.6.10 | 10 / 8 | |
| 0.6.9 | 10 / 8 | |
| 0.6.8 | 10 / 8 | |
| 0.6.7 | 10 / 8 | |
| 0.6.6 | 10 / 8 | |
| 0.6.5 | 10 / 8 | |
| 0.6.4 | 10 / 8 | |
| 0.6.3 | 10 / 8 | |
| 0.6.2 | 10 / 8 | |
| 0.6.1 | 10 / 8 | |
| 0.6.0 | 10 / 8 | |
| 0.5.23 | 10 / 7 | |
| 0.5.22 | 10 / 7 | |
| 0.5.21 | 10 / 7 | |
| 0.5.20 | 10 / 7 | |
| 0.5.19 | 10 / 7 | |
| 0.5.18 | 10 / 7 | |
| 0.5.17 | 10 / 7 | |
| 0.5.16 | 10 / 7 | |
| 0.5.15 | 10 / 7 | |
| 0.5.14 | 10 / 7 | |
| 0.5.13 | 10 / 7 | |
| 0.5.12 | 10 / 7 | |
| 0.5.11 | 10 / 7 |
v0.8.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: uifrnbot.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.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.
v0.6.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.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.