@fluentui/react-message-bar
Fluent UI MessageBar 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): Microsoft's Fluent UI monorepo packages are published without Sigstore provenance; this is consistent across all @fluentui/* packages and not a risk signal. | ai |
Versions (showing 100 of 100)
| Version | Deps | Published |
|---|---|---|
| 9.7.3 | 11 / 0 | |
| 9.7.2 | 11 / 0 | |
| 9.7.1 | 11 / 0 | |
| 9.7.0 | 11 / 0 | |
| 9.6.23 | 11 / 0 | |
| 9.6.22 | 11 / 0 | |
| 9.6.21 | 11 / 0 | |
| 9.6.20 | 11 / 0 | |
| 9.6.19 | 11 / 0 | |
| 9.6.18 | 11 / 0 | |
| 9.6.17 | 11 / 0 | |
| 9.6.16 | 11 / 5 | |
| 9.6.15 | 11 / 5 | |
| 9.6.14 | 11 / 5 | |
| 9.6.13 | 11 / 5 | |
| 9.6.12 | 11 / 5 | |
| 9.6.11 | 11 / 5 | |
| 9.6.10 | 11 / 5 | |
| 9.6.9 | 11 / 5 | |
| 9.6.8 | 11 / 5 | |
| 9.6.7 | 11 / 5 | |
| 9.6.6 | 10 / 5 | |
| 9.6.5 | 10 / 5 | |
| 9.6.4 | 10 / 5 | |
| 9.6.3 | 10 / 5 | |
| 9.6.2 | 10 / 5 | |
| 9.6.1 | 10 / 5 | |
| 9.6.0 | 10 / 5 | |
| 9.5.4 | 10 / 5 | |
| 9.5.3 | 10 / 4 | |
| 9.5.2 | 10 / 4 | |
| 9.5.1 | 10 / 4 | |
| 9.5.0 | 10 / 4 | |
| 9.4.9 | 10 / 4 | |
| 9.4.8 | 10 / 4 | |
| 9.4.7 | 10 / 4 | |
| 9.4.6 | 10 / 4 | |
| 9.4.5 | 10 / 4 | |
| 9.4.4 | 10 / 4 | |
| 9.4.3 | 10 / 4 | |
| 9.4.2 | 11 / 4 | |
| 9.4.1 | 11 / 4 | |
| 9.4.0 | 11 / 4 | |
| 9.3.3 | 11 / 4 | |
| 9.3.2 | 11 / 4 | |
| 9.3.1 | 11 / 4 | |
| 9.3.0 | 11 / 4 | |
| 9.2.19 | 10 / 4 | |
| 9.2.18 | 10 / 4 | |
| 9.2.17 | 10 / 4 | |
| 9.2.16 | 10 / 4 | |
| 9.2.15 | 10 / 4 | |
| 9.2.14 | 10 / 5 | |
| 9.2.13 | 10 / 5 | |
| 9.2.12 | 9 / 5 | |
| 9.2.11 | 9 / 5 | |
| 9.2.10 | 9 / 5 | |
| 9.2.9 | 9 / 5 | |
| 9.2.8 | 9 / 5 | |
| 9.2.7 | 9 / 5 | |
| 9.2.6 | 9 / 5 | |
| 9.2.5 | 9 / 5 | |
| 9.2.4 | 9 / 5 | |
| 9.2.3 | 9 / 5 | |
| 9.2.2 | 9 / 5 | |
| 9.2.1 | 9 / 5 | |
| 9.2.0 | 9 / 5 | |
| 9.1.1 | 9 / 5 | |
| 9.1.0 | 9 / 5 | |
| 9.0.30 | 9 / 5 | |
| 9.0.29 | 9 / 5 | |
| 9.0.28 | 9 / 5 | |
| 9.0.27 | 9 / 5 | |
| 9.0.26 | 9 / 5 | |
| 9.0.25 | 9 / 5 | |
| 9.0.24 | 9 / 5 | |
| 9.0.23 | 9 / 5 | |
| 9.0.22 | 9 / 5 | |
| 9.0.21 | 9 / 5 | |
| 9.0.20 | 9 / 5 | |
| 9.0.19 | 9 / 5 | |
| 9.0.18 | 9 / 5 | |
| 9.0.17 | 9 / 5 | |
| 9.0.16 | 9 / 5 | |
| 9.0.15 | 9 / 5 | |
| 9.0.14 | 9 / 5 | |
| 9.0.13 | 9 / 5 | |
| 9.0.12 | 9 / 5 | |
| 9.0.11 | 9 / 5 | |
| 9.0.10 | 9 / 5 | |
| 9.0.9 | 9 / 5 | |
| 9.0.8 | 9 / 5 | |
| 9.0.7 | 9 / 5 | |
| 9.0.6 | 9 / 5 | |
| 9.0.5 | 9 / 5 | |
| 9.0.4 | 9 / 5 | |
| 9.0.3 | 9 / 5 | |
| 9.0.2 | 9 / 5 | |
| 9.0.1 | 9 / 5 | |
| 9.0.0 | 9 / 5 |
v9.7.3
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.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.29
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.0.28
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.0.27
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.0.26
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.0.25
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.0.24
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.0.23
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.0.22
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.0.21
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.0.20
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.0.19
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.0.18
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.0.17
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.0.16
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.0.15
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.0.14
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.0.13
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.0.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.0.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.0.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.0.9
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.0.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.0.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.
v9.0.6
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.0.5
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.0.4
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.0.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.
v9.0.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.
v9.0.1
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.0.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.