@fkui/icon-lib-builder
Icon library builder
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): glob, sass, svgo are legitimate, well-known packages appropriate for an icon library builder. | ai | |
| dependencies | unvetted-dep:svgo | AI (dependencies): svgo is a standard SVG optimizer; expected and appropriate for an icon library builder. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 6.52.2 | 3 / 2 | |
| 6.52.0 | 3 / 2 | |
| 6.51.0 | 3 / 2 | |
| 6.50.0 | 3 / 2 | |
| 6.49.1 | 3 / 2 | |
| 6.49.0 | 3 / 2 | |
| 6.48.0 | 3 / 2 | |
| 6.47.0 | 3 / 0 | |
| 6.46.0 | 3 / 0 | |
| 6.45.0 | 3 / 0 | |
| 6.44.0 | 3 / 0 | |
| 6.43.0 | 3 / 0 | |
| 6.42.0 | 3 / 0 | |
| 6.40.0 | 3 / 0 | |
| 6.39.0 | 3 / 0 | |
| 6.37.0 | 3 / 0 | |
| 6.34.0 | 3 / 0 | |
| 6.32.1 | 3 / 0 | |
| 6.31.0 | 3 / 0 | |
| 6.30.0 | 3 / 0 | |
| 6.29.0 | 3 / 0 | |
| 6.28.0 | 3 / 0 | |
| 6.25.1 | 3 / 0 | |
| 6.25.0 | 3 / 0 | |
| 6.21.0 | 3 / 0 | |
| 6.19.1 | 3 / 0 | |
| 6.19.0 | 3 / 0 | |
| 6.17.0 | 3 / 0 | |
| 6.14.0 | 3 / 0 | |
| 6.13.0 | 3 / 0 | |
| 6.11.0 | 3 / 0 | |
| 6.9.0 | 3 / 0 | |
| 6.8.0 | 3 / 0 | |
| 6.7.0 | 0 / 2 | |
| 6.6.0 | 0 / 2 | |
| 6.5.0 | 0 / 2 | |
| 6.4.0 | 0 / 2 | |
| 6.3.0 | 0 / 2 | |
| 6.2.0 | 0 / 2 | |
| 6.1.0 | 0 / 2 | |
| 6.0.0 | 0 / 2 |
v6.52.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.52.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.