@fluentui-react-native/notification
add component-description
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): Microsoft FluentUI React Native monorepo packages are published via a bot without Sigstore provenance; this is consistent across all versions and not a security concern for this well-established project. | ai |
Versions (showing 51 of 220)
| Version | Deps | Published |
|---|---|---|
| 0.26.3 | 13 / 22 | |
| 0.26.1 | 13 / 22 | |
| 0.26.0 | 13 / 22 | |
| 0.25.29 | 13 / 17 | |
| 0.25.28 | 13 / 17 | |
| 0.25.27 | 13 / 17 | |
| 0.25.26 | 13 / 17 | |
| 0.25.25 | 13 / 17 | |
| 0.25.24 | 13 / 17 | |
| 0.25.23 | 13 / 17 | |
| 0.25.22 | 13 / 17 | |
| 0.25.21 | 13 / 17 | |
| 0.25.20 | 13 / 13 | |
| 0.25.19 | 13 / 13 | |
| 0.25.18 | 13 / 13 | |
| 0.25.17 | 13 / 13 | |
| 0.25.16 | 13 / 13 | |
| 0.25.15 | 13 / 13 | |
| 0.25.14 | 13 / 13 | |
| 0.25.13 | 13 / 13 | |
| 0.25.12 | 13 / 11 | |
| 0.25.11 | 13 / 9 | |
| 0.25.10 | 13 / 9 | |
| 0.25.9 | 13 / 9 | |
| 0.25.8 | 13 / 9 | |
| 0.25.7 | 13 / 9 | |
| 0.25.6 | 13 / 9 | |
| 0.25.5 | 13 / 9 | |
| 0.25.4 | 13 / 9 | |
| 0.25.3 | 13 / 9 | |
| 0.25.2 | 13 / 9 | |
| 0.25.1 | 13 / 9 | |
| 0.25.0 | 13 / 9 | |
| 0.24.18 | 13 / 8 | |
| 0.24.17 | 13 / 8 | |
| 0.24.16 | 13 / 8 | |
| 0.24.15 | 13 / 8 | |
| 0.24.14 | 13 / 8 | |
| 0.24.13 | 13 / 8 | |
| 0.24.12 | 13 / 8 | |
| 0.24.11 | 13 / 8 | |
| 0.24.10 | 13 / 8 | |
| 0.24.9 | 13 / 8 | |
| 0.24.8 | 13 / 8 | |
| 0.24.7 | 13 / 8 | |
| 0.24.6 | 13 / 8 | |
| 0.24.5 | 13 / 8 | |
| 0.24.4 | 13 / 8 | |
| 0.24.3 | 13 / 8 | |
| 0.24.2 | 13 / 8 | |
| 0.24.1 | 13 / 8 |
v0.25.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.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.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.