@fluentui/react-persona
React components for building web experiences
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Microsoft Fluent UI package with 1,299 days history; lack of Sigstore provenance is common and not a meaningful risk for this well-known publisher. | ai | |
| dependencies | unvetted-dep:@griffel/react | AI (dependencies): @griffel/react is the official CSS-in-JS library for Microsoft Fluent UI; a stable, expected dependency for this package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-badge | AI (dependencies): Sibling @fluentui/* package from the same Microsoft Fluent UI monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): Sibling @fluentui/* package from the same Microsoft Fluent UI monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-avatar | AI (dependencies): Sibling @fluentui/* package from the same Microsoft Fluent UI monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): Sibling @fluentui/* package from the same Microsoft Fluent UI monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): Sibling @fluentui/* package from the same Microsoft Fluent UI monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): Sibling @fluentui/* package from the same Microsoft Fluent UI monorepo; expected dependency. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 9.7.4 | 8 / 0 | |
| 9.7.3 | 8 / 0 | |
| 9.7.2 | 8 / 0 | |
| 9.7.1 | 8 / 0 | |
| 9.7.0 | 8 / 0 | |
| 9.6.2 | 8 / 0 | |
| 9.6.1 | 8 / 0 | |
| 9.6.0 | 8 / 0 | |
| 9.5.14 | 8 / 0 | |
| 9.5.13 | 8 / 4 | |
| 9.5.12 | 8 / 4 | |
| 9.5.11 | 8 / 4 | |
| 9.5.10 | 8 / 4 | |
| 9.5.9 | 8 / 4 | |
| 9.5.8 | 8 / 4 | |
| 9.5.7 | 8 / 4 | |
| 9.5.6 | 8 / 4 | |
| 9.5.5 | 8 / 4 | |
| 9.5.4 | 8 / 4 | |
| 9.5.3 | 8 / 4 | |
| 9.5.2 | 8 / 4 | |
| 9.5.1 | 8 / 4 | |
| 9.5.0 | 8 / 4 | |
| 9.4.7 | 8 / 4 | |
| 9.4.6 | 8 / 4 | |
| 9.4.5 | 8 / 4 | |
| 9.4.4 | 8 / 4 | |
| 9.4.3 | 8 / 4 | |
| 9.4.2 | 8 / 4 | |
| 9.4.1 | 8 / 4 | |
| 9.4.0 | 8 / 4 | |
| 9.3.9 | 8 / 4 | |
| 9.3.8 | 8 / 4 | |
| 9.3.7 | 8 / 4 |
v9.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.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.
v9.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.