← Home

@fluentui-react-native/stack

A cross-platform opinionated Fluent Text component

18
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jasonvmorseacoatesuifrnbothansenyy

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 18 of 18)

Version Deps Published
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

v0.11.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.11.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.11.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.10.22

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.16

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.