@vaadin/icon
Web component for creating 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:lit | AI (dependencies): lit is a well-established Google-maintained web components library and a standard dependency for Vaadin web components; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Vaadin publishes from a known GitHub monorepo; lack of Sigstore provenance is common and not a risk signal for this established publisher. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 25.1.3 | 4 / 6 | |
| 25.1.2 | 4 / 6 | |
| 25.1.1 | 4 / 6 | |
| 25.1.0 | 4 / 6 | |
| 25.0.12 | 4 / 6 | |
| 25.0.11 | 4 / 6 | |
| 25.0.10 | 4 / 6 | |
| 25.0.9 | 4 / 6 | |
| 25.0.8 | 4 / 6 | |
| 25.0.7 | 4 / 6 | |
| 25.0.6 | 4 / 6 | |
| 25.0.5 | 4 / 6 | |
| 25.0.4 | 4 / 6 | |
| 25.0.3 | 4 / 6 | |
| 25.0.2 | 4 / 5 | |
| 25.0.1 | 4 / 5 | |
| 25.0.0 | 4 / 5 | |
| 24.10.3 | 6 / 4 | |
| 24.10.2 | 6 / 4 | |
| 24.10.1 | 6 / 4 | |
| 24.10.0 | 6 / 4 | |
| 24.9.15 | 6 / 4 | |
| 24.9.14 | 6 / 4 | |
| 24.9.13 | 6 / 4 | |
| 24.9.12 | 6 / 4 | |
| 24.9.11 | 6 / 4 | |
| 24.9.10 | 6 / 4 | |
| 24.9.9 | 6 / 4 | |
| 24.9.8 | 6 / 4 | |
| 24.9.7 | 6 / 4 | |
| 24.9.6 | 6 / 4 | |
| 24.9.5 | 6 / 4 | |
| 24.9.4 | 6 / 4 | |
| 24.9.3 | 6 / 4 | |
| 24.8.14 | 6 / 4 | |
| 24.8.13 | 6 / 4 | |
| 24.8.12 | 6 / 4 | |
| 24.8.11 | 6 / 4 | |
| 24.8.10 | 6 / 4 | |
| 23.6.4 | 5 / 3 | |
| 23.6.3 | 5 / 3 |
v25.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.9.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.