@fluentui-react-native/avatar
A cross-platform Avatar component using the Fluent Design System
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): Consistent with monorepo component release cadence, no suspicious content. | ai | |
| provenance | missing-githead | AI (provenance): Trusted bot publisher, monorepo CI quirk, no behavioral risk. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party fluentui-react-native sibling package. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft monorepo package published via automation bot; lack of Sigstore provenance is consistent across all versions and poses no material risk. | ai |
Versions (showing 51 of 204)
| Version | Deps | Published |
|---|---|---|
| 1.13.5 | 10 / 16 | |
| 1.13.4 | 9 / 17 | |
| 1.13.3 | 9 / 21 | |
| 1.13.1 | 9 / 21 | |
| 1.13.0 | 9 / 21 | |
| 1.12.23 | 8 / 16 | |
| 1.12.22 | 8 / 16 | |
| 1.12.21 | 8 / 16 | |
| 1.12.20 | 8 / 16 | |
| 1.12.19 | 8 / 16 | |
| 1.12.18 | 8 / 16 | |
| 1.12.17 | 8 / 12 | |
| 1.12.16 | 8 / 12 | |
| 1.12.15 | 8 / 12 | |
| 1.12.14 | 8 / 12 | |
| 1.12.13 | 8 / 12 | |
| 1.12.12 | 8 / 12 | |
| 1.12.11 | 8 / 12 | |
| 1.12.10 | 8 / 12 | |
| 1.12.9 | 8 / 10 | |
| 1.12.8 | 8 / 8 | |
| 1.12.7 | 8 / 8 | |
| 1.12.6 | 8 / 8 | |
| 1.12.5 | 8 / 8 | |
| 1.12.4 | 8 / 8 | |
| 1.12.3 | 8 / 8 | |
| 1.12.2 | 8 / 8 | |
| 1.12.1 | 8 / 8 | |
| 1.12.0 | 8 / 8 | |
| 1.11.15 | 8 / 7 | |
| 1.11.14 | 8 / 7 | |
| 1.11.13 | 8 / 7 | |
| 1.11.12 | 8 / 7 | |
| 1.11.11 | 8 / 7 | |
| 1.11.10 | 8 / 7 | |
| 1.11.9 | 8 / 7 | |
| 1.11.8 | 8 / 7 | |
| 1.11.7 | 8 / 7 | |
| 1.11.6 | 8 / 7 | |
| 1.11.5 | 8 / 7 | |
| 1.11.4 | 8 / 7 | |
| 1.11.3 | 8 / 7 | |
| 1.11.2 | 8 / 7 | |
| 1.11.1 | 8 / 7 | |
| 1.11.0 | 8 / 7 | |
| 1.10.18 | 8 / 6 | |
| 1.10.17 | 8 / 6 | |
| 1.10.16 | 8 / 6 | |
| 1.10.15 | 8 / 6 | |
| 1.10.14 | 8 / 6 | |
| 1.10.13 | 8 / 6 |
v1.13.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.
v1.12.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.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.
v1.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.