@fluentui-react-native/experimental-avatar
A cross-platform Avatar component using the Fluent Design System. Currently only implemented on iOS
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Monorepo CI publish variance for trusted Microsoft bot; not a lineage regression to malicious actor. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a first-party sibling package in the same monorepo/org. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/framework | AI (dependencies): Sibling package within the same microsoft/fluentui-react-native monorepo; not a third-party or suspicious dependency. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft package published via automation bot; lack of Sigstore provenance is not a meaningful risk signal here. | ai |
Versions (showing 100 of 241)
| Version | Deps | Published |
|---|---|---|
| 0.22.5 | 2 / 13 | |
| 0.22.4 | 1 / 14 | |
| 0.22.3 | 1 / 17 | |
| 0.22.1 | 1 / 17 | |
| 0.22.0 | 1 / 17 | |
| 0.21.19 | 1 / 13 | |
| 0.21.18 | 1 / 13 | |
| 0.21.17 | 1 / 13 | |
| 0.21.16 | 1 / 13 | |
| 0.21.15 | 1 / 13 | |
| 0.21.14 | 1 / 13 | |
| 0.21.13 | 1 / 10 | |
| 0.21.12 | 1 / 10 | |
| 0.21.11 | 1 / 10 | |
| 0.21.10 | 1 / 10 | |
| 0.21.9 | 1 / 10 | |
| 0.21.8 | 1 / 10 | |
| 0.21.7 | 1 / 10 | |
| 0.21.6 | 1 / 10 | |
| 0.21.5 | 1 / 7 | |
| 0.21.4 | 1 / 6 | |
| 0.21.3 | 1 / 6 | |
| 0.21.2 | 1 / 6 | |
| 0.21.1 | 1 / 6 | |
| 0.21.0 | 1 / 6 | |
| 0.20.13 | 1 / 5 | |
| 0.20.12 | 1 / 5 | |
| 0.20.11 | 2 / 5 | |
| 0.20.10 | 2 / 5 | |
| 0.20.9 | 2 / 5 | |
| 0.20.8 | 2 / 5 | |
| 0.20.7 | 2 / 5 | |
| 0.20.6 | 2 / 5 | |
| 0.20.5 | 2 / 5 | |
| 0.20.4 | 2 / 5 | |
| 0.20.3 | 2 / 5 | |
| 0.20.2 | 2 / 5 | |
| 0.20.1 | 2 / 5 | |
| 0.20.0 | 2 / 5 | |
| 0.19.11 | 2 / 4 | |
| 0.19.10 | 2 / 4 | |
| 0.19.9 | 2 / 4 | |
| 0.19.8 | 2 / 4 | |
| 0.19.7 | 2 / 4 | |
| 0.19.6 | 2 / 4 | |
| 0.19.5 | 2 / 4 | |
| 0.19.4 | 2 / 4 | |
| 0.19.3 | 2 / 4 | |
| 0.19.2 | 2 / 4 | |
| 0.19.1 | 2 / 4 | |
| 0.19.0 | 2 / 4 | |
| 0.18.0 | 2 / 4 | |
| 0.17.25 | 2 / 5 | |
| 0.17.24 | 2 / 5 | |
| 0.17.23 | 2 / 5 | |
| 0.17.22 | 2 / 5 | |
| 0.17.21 | 2 / 5 | |
| 0.17.20 | 2 / 5 | |
| 0.17.19 | 2 / 5 | |
| 0.17.18 | 2 / 5 | |
| 0.17.17 | 2 / 5 | |
| 0.17.16 | 2 / 5 | |
| 0.17.15 | 2 / 5 | |
| 0.17.14 | 2 / 5 | |
| 0.17.13 | 2 / 5 | |
| 0.17.12 | 2 / 5 | |
| 0.17.11 | 2 / 5 | |
| 0.17.10 | 2 / 5 | |
| 0.17.9 | 2 / 5 | |
| 0.17.8 | 2 / 5 | |
| 0.17.7 | 2 / 5 | |
| 0.17.6 | 2 / 5 | |
| 0.17.5 | 2 / 5 | |
| 0.17.4 | 2 / 5 | |
| 0.17.3 | 2 / 5 | |
| 0.17.2 | 2 / 5 | |
| 0.17.1 | 2 / 5 | |
| 0.17.0 | 2 / 5 | |
| 0.16.31 | 2 / 5 | |
| 0.16.30 | 2 / 5 | |
| 0.16.29 | 2 / 5 | |
| 0.16.28 | 2 / 5 | |
| 0.16.27 | 2 / 5 | |
| 0.16.26 | 2 / 5 | |
| 0.16.25 | 2 / 5 | |
| 0.16.24 | 2 / 5 | |
| 0.16.23 | 2 / 5 | |
| 0.16.22 | 2 / 5 | |
| 0.16.21 | 2 / 5 | |
| 0.16.20 | 2 / 5 | |
| 0.16.19 | 2 / 5 | |
| 0.16.18 | 2 / 5 | |
| 0.16.17 | 2 / 5 | |
| 0.16.16 | 2 / 5 | |
| 0.16.15 | 2 / 5 | |
| 0.16.14 | 2 / 5 | |
| 0.16.13 | 2 / 5 | |
| 0.16.12 | 2 / 5 | |
| 0.16.11 | 2 / 5 | |
| 0.16.10 | 2 / 5 |
v0.22.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.21.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.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.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.23
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.17.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.