@fluentui/react-icons
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@griffel/react | AI (dependencies): @griffel/react is Microsoft's own CSS-in-JS library, a core dependency of the Fluent UI ecosystem. It is a legitimate, well-known package and not a risk for this package. | ai |
Versions (showing 100 of 139)
| Version | Deps | Published |
|---|---|---|
| 2.0.333 | 2 / 14 | |
| 2.0.332 | 2 / 14 | |
| 2.0.331 | 2 / 15 | |
| 2.0.330 | 2 / 16 | |
| 2.0.329 | 2 / 16 | |
| 2.0.328 | 2 / 16 | |
| 2.0.327 | 2 / 16 | |
| 2.0.326 | 2 / 15 | |
| 2.0.325 | 2 / 15 | |
| 2.0.324 | 2 / 15 | |
| 2.0.323 | 2 / 15 | |
| 2.0.322 | 2 / 22 | |
| 2.0.321 | 2 / 22 | |
| 2.0.320 | 2 / 22 | |
| 2.0.319 | 2 / 22 | |
| 2.0.318 | 2 / 23 | |
| 2.0.317 | 2 / 23 | |
| 2.0.316 | 2 / 23 | |
| 2.0.315 | 2 / 23 | |
| 2.0.314 | 2 / 23 | |
| 2.0.313 | 2 / 21 | |
| 2.0.312 | 2 / 20 | |
| 2.0.311 | 2 / 20 | |
| 2.0.310 | 2 / 17 | |
| 2.0.309 | 2 / 17 | |
| 2.0.308 | 2 / 17 | |
| 2.0.307 | 2 / 17 | |
| 2.0.306 | 2 / 14 | |
| 2.0.305 | 2 / 14 | |
| 2.0.304 | 2 / 14 | |
| 2.0.303 | 2 / 14 | |
| 2.0.302 | 2 / 14 | |
| 2.0.301 | 2 / 14 | |
| 2.0.300 | 2 / 14 | |
| 2.0.299 | 2 / 14 | |
| 2.0.298 | 2 / 14 | |
| 2.0.297 | 2 / 14 | |
| 2.0.296 | 2 / 14 | |
| 2.0.295 | 2 / 14 | |
| 2.0.294 | 2 / 14 | |
| 2.0.292 | 2 / 14 | |
| 2.0.279 | 2 / 14 | |
| 2.0.274 | 2 / 14 | |
| 2.0.271 | 2 / 14 | |
| 2.0.270 | 2 / 14 | |
| 2.0.269 | 2 / 14 | |
| 2.0.268 | 2 / 14 | |
| 2.0.267 | 2 / 14 | |
| 2.0.266 | 2 / 14 | |
| 2.0.265 | 2 / 14 | |
| 2.0.264 | 2 / 14 | |
| 2.0.263 | 2 / 14 | |
| 2.0.262 | 2 / 14 | |
| 2.0.261 | 2 / 14 | |
| 2.0.260 | 2 / 14 | |
| 2.0.259 | 2 / 14 | |
| 2.0.258 | 2 / 14 | |
| 2.0.257 | 2 / 14 | |
| 2.0.256 | 2 / 14 | |
| 2.0.255 | 2 / 14 | |
| 2.0.254 | 2 / 14 | |
| 2.0.253 | 2 / 14 | |
| 2.0.252 | 2 / 14 | |
| 2.0.251 | 2 / 14 | |
| 2.0.250 | 2 / 14 | |
| 2.0.249 | 2 / 14 | |
| 2.0.248 | 2 / 14 | |
| 2.0.247 | 2 / 14 | |
| 2.0.246 | 2 / 14 | |
| 2.0.245 | 2 / 14 | |
| 2.0.244 | 2 / 14 | |
| 2.0.243 | 2 / 14 | |
| 2.0.242 | 2 / 14 | |
| 2.0.241 | 2 / 14 | |
| 2.0.240 | 2 / 14 | |
| 2.0.239 | 2 / 14 | |
| 2.0.238 | 2 / 14 | |
| 2.0.237 | 2 / 14 | |
| 2.0.236 | 2 / 14 | |
| 2.0.235 | 2 / 14 | |
| 2.0.234 | 2 / 14 | |
| 2.0.233 | 2 / 14 | |
| 2.0.232 | 2 / 14 | |
| 2.0.231 | 2 / 14 | |
| 2.0.230 | 2 / 14 | |
| 2.0.229 | 2 / 14 | |
| 2.0.228 | 2 / 14 | |
| 2.0.227 | 2 / 14 | |
| 2.0.226 | 2 / 14 | |
| 2.0.225 | 2 / 14 | |
| 2.0.224 | 2 / 14 | |
| 2.0.223 | 2 / 14 | |
| 2.0.222 | 2 / 14 | |
| 2.0.221 | 2 / 14 | |
| 2.0.220 | 2 / 14 | |
| 2.0.219 | 2 / 14 | |
| 2.0.218 | 2 / 14 | |
| 2.0.217 | 2 / 14 | |
| 2.0.216 | 2 / 14 | |
| 2.0.215 | 2 / 14 |
v2.0.333
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.332
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.331
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.297
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.296
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.295
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.294
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.292
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.279
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.274
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.271
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.270
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.269
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.268
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.267
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.266
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.265
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.264
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.263
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.262
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.261
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.260
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.259
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.258
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.257
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.256
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.255
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.254
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.253
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.252
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.251
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.250
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.249
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.248
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.247
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.246
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.245
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.244
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.243
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.242
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.241
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.240
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.239
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.238
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.237
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.236
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.235
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.234
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.233
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.232
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.231
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.230
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.229
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.228
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.227
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.226
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.225
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.224
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.223
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.222
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.221
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.220
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.219
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.218
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.217
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.216
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.215
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.