@fluentui/react-file-type-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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Microsoft FluentUI monorepo; no provenance is consistent across all versions of this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; declared as a direct dep and commonly used implicitly in compiled output. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 8.18.1 | 3 / 0 | |
| 8.18.0 | 3 / 0 | |
| 8.17.0 | 3 / 0 | |
| 8.16.0 | 3 / 0 | |
| 8.15.3 | 3 / 3 | |
| 8.15.2 | 3 / 3 | |
| 8.15.1 | 3 / 3 | |
| 8.15.0 | 3 / 3 | |
| 8.14.2 | 3 / 3 | |
| 8.14.1 | 3 / 3 | |
| 8.14.0 | 3 / 3 | |
| 8.13.3 | 3 / 3 | |
| 8.13.2 | 3 / 3 | |
| 8.13.1 | 3 / 3 | |
| 8.13.0 | 3 / 3 | |
| 8.12.9 | 3 / 3 | |
| 8.12.8 | 3 / 3 | |
| 8.12.7 | 3 / 3 | |
| 8.12.6 | 3 / 3 | |
| 8.12.5 | 3 / 3 | |
| 8.12.4 | 3 / 3 | |
| 8.12.3 | 3 / 3 | |
| 8.12.2 | 3 / 3 | |
| 8.12.1 | 3 / 3 | |
| 8.12.0 | 3 / 3 | |
| 8.11.21 | 3 / 3 | |
| 8.11.20 | 3 / 3 | |
| 8.11.19 | 3 / 3 | |
| 8.11.18 | 3 / 3 | |
| 8.11.17 | 3 / 3 | |
| 8.11.16 | 3 / 3 | |
| 8.11.15 | 3 / 3 | |
| 8.11.14 | 3 / 3 | |
| 8.11.13 | 3 / 3 | |
| 8.11.12 | 3 / 3 | |
| 8.11.11 | 3 / 3 | |
| 8.11.10 | 3 / 3 |
v8.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.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.