@fluentui-react-native/stack
A cross-platform opinionated Fluent Text component
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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Normal monorepo release churn, no suspicious content indicated. | ai | |
| provenance | missing-githead | AI (provenance): Monorepo bulk-publish by trusted bot; no malicious behavior indicated. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party sibling package within same monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft monorepo package published via CI bot; lack of Sigstore provenance is consistent across all versions and not a meaningful risk signal here. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/framework | AI (dependencies): Sibling package within the same Microsoft FluentUI React Native monorepo; unvetted flag is expected for internal monorepo deps. | ai | |
| dependencies | unvetted-dep:@uifabricshared/foundation-compose | AI (dependencies): Part of the same Microsoft FluentUI/UIFabric ecosystem; unvetted flag is expected for these internal monorepo dependencies. | ai |
Versions (showing 51 of 228)
| Version | Deps | Published |
|---|---|---|
| 0.11.5 | 8 / 15 | |
| 0.11.4 | 7 / 16 | |
| 0.11.3 | 7 / 20 | |
| 0.11.1 | 7 / 20 | |
| 0.11.0 | 7 / 20 | |
| 0.10.22 | 7 / 15 | |
| 0.10.21 | 7 / 15 | |
| 0.10.20 | 7 / 15 | |
| 0.10.19 | 7 / 15 | |
| 0.10.18 | 7 / 15 | |
| 0.10.17 | 7 / 15 | |
| 0.10.16 | 7 / 11 | |
| 0.10.15 | 7 / 11 | |
| 0.10.14 | 7 / 11 | |
| 0.10.13 | 7 / 11 | |
| 0.10.12 | 7 / 11 | |
| 0.10.11 | 7 / 11 | |
| 0.10.10 | 7 / 11 | |
| 0.10.9 | 7 / 11 | |
| 0.10.8 | 7 / 9 | |
| 0.10.7 | 7 / 7 | |
| 0.10.6 | 7 / 7 | |
| 0.10.5 | 7 / 7 | |
| 0.10.4 | 7 / 7 | |
| 0.10.3 | 7 / 7 | |
| 0.10.2 | 7 / 7 | |
| 0.10.1 | 7 / 7 | |
| 0.10.0 | 7 / 7 | |
| 0.9.14 | 7 / 6 | |
| 0.9.13 | 7 / 6 | |
| 0.9.12 | 7 / 6 | |
| 0.9.11 | 7 / 6 | |
| 0.9.10 | 7 / 6 | |
| 0.9.9 | 7 / 6 | |
| 0.9.8 | 7 / 6 | |
| 0.9.7 | 7 / 6 | |
| 0.9.6 | 7 / 6 | |
| 0.9.5 | 7 / 6 | |
| 0.9.4 | 7 / 6 | |
| 0.9.3 | 7 / 6 | |
| 0.9.2 | 7 / 6 | |
| 0.9.1 | 7 / 6 | |
| 0.9.0 | 7 / 6 | |
| 0.8.16 | 7 / 5 | |
| 0.8.15 | 7 / 5 | |
| 0.8.14 | 7 / 5 | |
| 0.8.13 | 7 / 5 | |
| 0.8.12 | 7 / 5 | |
| 0.8.11 | 7 / 5 | |
| 0.8.10 | 7 / 5 | |
| 0.8.9 | 7 / 5 |
v0.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: uifrnbot.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
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.10.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.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.