@fluentui-react-native/icon
A cross-platform Icon 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Microsoft monorepo package published via bot; lack of Sigstore provenance is consistent across all versions and not a risk signal for this package. | ai |
Versions (showing 51 of 232)
| Version | Deps | Published |
|---|---|---|
| 0.22.3 | 4 / 21 | |
| 0.22.1 | 4 / 21 | |
| 0.22.0 | 4 / 21 | |
| 0.21.23 | 3 / 17 | |
| 0.21.22 | 3 / 17 | |
| 0.21.21 | 3 / 17 | |
| 0.21.20 | 3 / 17 | |
| 0.21.19 | 3 / 17 | |
| 0.21.18 | 3 / 17 | |
| 0.21.17 | 3 / 13 | |
| 0.21.16 | 3 / 13 | |
| 0.21.15 | 3 / 13 | |
| 0.21.14 | 3 / 13 | |
| 0.21.13 | 3 / 13 | |
| 0.21.12 | 3 / 13 | |
| 0.21.11 | 3 / 13 | |
| 0.21.10 | 3 / 13 | |
| 0.21.9 | 3 / 11 | |
| 0.21.8 | 3 / 9 | |
| 0.21.7 | 3 / 9 | |
| 0.21.6 | 3 / 9 | |
| 0.21.5 | 3 / 9 | |
| 0.21.4 | 3 / 9 | |
| 0.21.3 | 3 / 9 | |
| 0.21.2 | 3 / 9 | |
| 0.21.1 | 3 / 9 | |
| 0.21.0 | 3 / 9 | |
| 0.20.15 | 3 / 8 | |
| 0.20.14 | 3 / 8 | |
| 0.20.13 | 3 / 8 | |
| 0.20.12 | 3 / 8 | |
| 0.20.11 | 3 / 8 | |
| 0.20.10 | 3 / 8 | |
| 0.20.9 | 3 / 8 | |
| 0.20.8 | 3 / 8 | |
| 0.20.7 | 3 / 8 | |
| 0.20.6 | 3 / 8 | |
| 0.20.5 | 3 / 8 | |
| 0.20.4 | 3 / 8 | |
| 0.20.3 | 3 / 8 | |
| 0.20.2 | 3 / 8 | |
| 0.20.1 | 3 / 8 | |
| 0.20.0 | 3 / 8 | |
| 0.19.16 | 3 / 7 | |
| 0.19.15 | 3 / 7 | |
| 0.19.14 | 3 / 7 | |
| 0.19.13 | 3 / 7 | |
| 0.19.12 | 3 / 7 | |
| 0.19.11 | 3 / 7 | |
| 0.19.10 | 3 / 7 | |
| 0.19.9 | 3 / 7 |
v0.21.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.5
1 finding[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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.14
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.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.12
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.