@vaadin/component-base
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 Google's official web components library; a standard, legitimate dependency for Vaadin web components. | ai | |
| dependencies | unvetted-dep:@open-wc/dedupe-mixin | AI (dependencies): @open-wc/dedupe-mixin is from the well-known Open Web Components project; a standard dependency in the web components ecosystem. | ai | |
| dependencies | unvetted-dep:@vaadin/vaadin-usage-statistics | AI (dependencies): Same-org Vaadin package for usage statistics; a standard companion dependency across all Vaadin components. | ai | |
| dependencies | unvetted-dep:@vaadin/vaadin-development-mode-detector | AI (dependencies): Same-org Vaadin package for dev-mode detection; a standard companion dependency across all Vaadin components. | ai | |
| phantom-deps | phantom-dep:@vaadin/vaadin-development-mode-detector | AI (phantom-deps): Declared but not directly imported; consistent with Vaadin's pattern of optional/conditional dev-mode detection across their component suite. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 25.1.3 | 4 / 4 | |
| 25.1.2 | 4 / 4 | |
| 25.1.1 | 4 / 4 | |
| 25.1.0 | 4 / 4 | |
| 25.0.12 | 4 / 4 | |
| 25.0.11 | 4 / 4 | |
| 25.0.10 | 4 / 4 | |
| 25.0.9 | 4 / 4 | |
| 25.0.8 | 4 / 4 | |
| 25.0.7 | 4 / 4 | |
| 25.0.6 | 4 / 4 | |
| 25.0.5 | 4 / 4 | |
| 25.0.4 | 4 / 4 | |
| 25.0.3 | 4 / 4 | |
| 25.0.2 | 4 / 4 | |
| 25.0.1 | 4 / 4 | |
| 25.0.0 | 4 / 4 | |
| 24.10.3 | 5 / 4 | |
| 24.10.2 | 5 / 4 | |
| 24.10.1 | 5 / 4 | |
| 24.10.0 | 5 / 4 | |
| 24.9.15 | 5 / 4 | |
| 24.9.14 | 5 / 4 | |
| 24.9.13 | 5 / 4 | |
| 24.9.12 | 5 / 4 | |
| 24.9.11 | 5 / 4 | |
| 24.9.10 | 5 / 4 | |
| 24.9.9 | 5 / 4 | |
| 24.9.8 | 5 / 4 | |
| 24.9.7 | 5 / 4 | |
| 24.9.6 | 5 / 4 | |
| 24.9.5 | 5 / 4 | |
| 24.9.4 | 5 / 4 | |
| 24.9.3 | 5 / 4 | |
| 24.8.14 | 5 / 4 | |
| 24.8.13 | 5 / 4 | |
| 24.8.12 | 5 / 4 | |
| 24.8.11 | 5 / 4 | |
| 24.8.10 | 5 / 4 | |
| 23.6.4 | 5 / 3 | |
| 23.6.3 | 5 / 3 |
v25.1.3
1 findingPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.12
1 findingPackage 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.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.