@vaadin/vaadin-lumo-styles
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 |
|---|---|---|---|---|
| license | uncommon-license:https://vaadin.com/commercial-license-and-service-terms | AI (license): Vaadin commercial license is well-known and expected for all @vaadin/* packages. Stable across all versions. | ai | |
| source-diff | obfuscated-file:font-icons.js | AI (source-diff): The long line is a base64-encoded WOFF icon font embedded in a CSS font-face declaration — standard practice for icon font packages like Vaadin Lumo. Not obfuscated code. | ai | |
| phantom-deps | phantom-dep:@polymer/polymer | AI (phantom-deps): @polymer/polymer is a legitimate declared dependency for this Polymer-based web components package; referenced in config files as expected for Polymer component infrastructure. | ai | |
| dependencies | unvetted-dep:@vaadin/icon | AI (dependencies): @vaadin/icon is a sibling package from the same Vaadin monorepo and publisher; this dependency is expected and stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Vaadin publishes from their official monorepo; lack of Sigstore provenance is consistent across their packages and not a security concern here. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 25.1.4 | 3 / 4 | |
| 25.1.3 | 3 / 4 | |
| 25.1.2 | 3 / 4 | |
| 25.1.1 | 3 / 4 | |
| 25.1.0 | 3 / 4 | |
| 25.0.13 | 3 / 4 | |
| 25.0.12 | 3 / 4 | |
| 25.0.11 | 3 / 4 | |
| 25.0.10 | 3 / 4 | |
| 25.0.9 | 3 / 4 | |
| 25.0.8 | 3 / 4 | |
| 25.0.7 | 3 / 4 | |
| 25.0.5 | 3 / 4 | |
| 25.0.4 | 3 / 4 | |
| 25.0.3 | 3 / 4 | |
| 25.0.2 | 3 / 4 | |
| 25.0.1 | 3 / 10 | |
| 25.0.0 | 3 / 10 | |
| 24.10.4 | 4 / 5 | |
| 24.10.3 | 4 / 5 | |
| 24.10.2 | 4 / 5 | |
| 24.10.1 | 4 / 5 | |
| 24.10.0 | 4 / 5 | |
| 24.9.16 | 4 / 5 | |
| 24.9.15 | 4 / 5 | |
| 24.9.14 | 4 / 5 | |
| 24.9.13 | 4 / 5 | |
| 24.9.12 | 4 / 5 | |
| 24.9.11 | 4 / 5 | |
| 24.9.10 | 4 / 5 | |
| 24.9.9 | 4 / 5 | |
| 24.9.8 | 4 / 5 | |
| 24.9.7 | 4 / 5 | |
| 24.9.6 | 4 / 5 | |
| 24.9.5 | 4 / 5 | |
| 24.9.4 | 4 / 5 | |
| 24.9.3 | 4 / 5 | |
| 24.8.14 | 4 / 5 | |
| 24.8.13 | 4 / 5 | |
| 24.8.12 | 4 / 5 | |
| 24.8.11 | 4 / 5 | |
| 24.8.10 | 4 / 5 | |
| 23.6.4 | 5 / 5 | |
| 23.6.3 | 5 / 5 |
v25.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v24.10.4
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.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.