@fluentui/react-icons-compat
Package for icon utility methods used by font and svg 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): SWC runtime helper; implicit dependency from transpilation. | ai | |
| phantom-deps | phantom-dep:@griffel/react | AI (phantom-deps): Config-referenced styling dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@fluentui/react-theme | AI (phantom-deps): Same-org peer utility; stable monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@fluentui/react-jsx-runtime | AI (phantom-deps): Same-org peer utility; stable monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@fluentui/react-shared-contexts | AI (phantom-deps): Same-org peer utility; stable monorepo pattern. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 0.2.21 | 6 / 0 | |
| 0.2.20 | 6 / 0 | |
| 0.2.19 | 6 / 0 | |
| 0.2.18 | 6 / 0 | |
| 0.2.17 | 6 / 0 | |
| 0.2.16 | 6 / 0 | |
| 0.2.15 | 6 / 4 | |
| 0.2.14 | 6 / 4 | |
| 0.2.13 | 6 / 4 | |
| 0.2.12 | 6 / 4 | |
| 0.2.11 | 6 / 4 | |
| 0.2.10 | 6 / 4 | |
| 0.2.9 | 6 / 4 | |
| 0.2.8 | 6 / 4 | |
| 0.2.7 | 6 / 4 | |
| 0.2.6 | 6 / 4 | |
| 0.2.5 | 6 / 4 | |
| 0.2.4 | 6 / 4 | |
| 0.2.3 | 6 / 4 | |
| 0.2.2 | 6 / 4 | |
| 0.2.1 | 6 / 4 | |
| 0.2.0 | 6 / 4 | |
| 0.1.13 | 6 / 4 | |
| 0.1.12 | 6 / 4 | |
| 0.1.11 | 6 / 4 | |
| 0.1.10 | 6 / 4 | |
| 0.1.9 | 6 / 4 | |
| 0.1.8 | 6 / 4 | |
| 0.1.7 | 6 / 4 | |
| 0.1.6 | 6 / 4 | |
| 0.1.5 | 6 / 4 | |
| 0.1.4 | 6 / 4 | |
| 0.1.3 | 6 / 5 | |
| 0.1.2 | 6 / 5 | |
| 0.1.1 | 6 / 5 | |
| 0.1.0 | 6 / 5 |
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.