@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 28 of 228)
| Version | Deps | Published |
|---|---|---|
| 0.5.1 | 7 / 5 | |
| 0.5.0 | 7 / 5 | |
| 0.4.2 | 7 / 5 | |
| 0.4.1 | 7 / 5 | |
| 0.4.0 | 7 / 5 | |
| 0.3.2 | 7 / 5 | |
| 0.3.1 | 7 / 5 | |
| 0.3.0 | 7 / 5 | |
| 0.2.19 | 7 / 5 | |
| 0.2.18 | 7 / 5 | |
| 0.2.17 | 7 / 5 | |
| 0.2.16 | 7 / 5 | |
| 0.2.15 | 7 / 5 | |
| 0.2.14 | 7 / 5 | |
| 0.2.13 | 7 / 5 | |
| 0.2.12 | 7 / 5 | |
| 0.2.11 | 7 / 5 | |
| 0.2.10 | 7 / 5 | |
| 0.2.9 | 7 / 5 | |
| 0.2.8 | 7 / 5 | |
| 0.2.7 | 7 / 5 | |
| 0.2.6 | 7 / 5 | |
| 0.2.5 | 7 / 5 | |
| 0.2.4 | 7 / 5 | |
| 0.2.3 | 7 / 5 | |
| 0.2.2 | 3 / 5 | |
| 0.2.1 | 3 / 5 | |
| 0.2.0 | 3 / 5 |
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.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.2.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.