@vaadin/vaadin
Vaadin components is an evolving set of open sourced custom HTML elements for building mobile and desktop web applications in modern browsers.
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:@vaadin/cookie-consent | AI (dependencies): Same-org Vaadin component following the standard versioning pattern; consistent with all other deps in this umbrella package. | ai | |
| phantom-deps | phantom-dep:@vaadin/vaadin-grid-pro | AI (phantom-deps): First-party @vaadin alias; meta-package re-exports deps without direct imports. | ai | |
| phantom-deps | phantom-dep:@vaadin/vaadin-charts | AI (phantom-deps): First-party @vaadin alias; meta-package re-exports deps without direct imports. | ai | |
| phantom-deps | phantom-dep:@vaadin/vaadin-cookie-consent | AI (phantom-deps): First-party @vaadin alias; meta-package re-exports deps without direct imports. | ai | |
| phantom-deps | phantom-dep:@vaadin/vaadin-crud | AI (phantom-deps): First-party @vaadin alias; meta-package re-exports deps without direct imports. | ai | |
| phantom-deps | phantom-dep:@vaadin/vaadin-board | AI (phantom-deps): First-party @vaadin alias; meta-package re-exports deps without direct imports. | ai | |
| phantom-deps | phantom-dep:@vaadin/vaadin-rich-text-editor | AI (phantom-deps): First-party @vaadin alias; meta-package re-exports deps without direct imports. | ai | |
| dependencies | unvetted-dep:@vaadin/vaadin-confirm-dialog | AI (dependencies): Official Vaadin scoped package; part of the Vaadin 14 LTS component set. | ai | |
| dependencies | unvetted-dep:@vaadin/vaadin-crud | AI (dependencies): Official Vaadin scoped package; part of the Vaadin 14 LTS component set. | ai | |
| dependencies | unvetted-dep:@vaadin/vaadin-board | AI (dependencies): Official Vaadin scoped package; part of the Vaadin 14 LTS component set. | ai | |
| dependencies | unvetted-dep:@vaadin/vaadin-charts | AI (dependencies): Official Vaadin scoped package; part of the Vaadin 14 LTS component set. | ai | |
| dependencies | unvetted-dep:@vaadin/vaadin-grid-pro | AI (dependencies): Official Vaadin scoped package; part of the Vaadin 14 LTS component set. | ai | |
| dependencies | unvetted-dep:@vaadin/vaadin-cookie-consent | AI (dependencies): Official Vaadin scoped package; part of the Vaadin 14 LTS component set. | ai | |
| dependencies | unvetted-dep:@vaadin/vaadin-rich-text-editor | AI (dependencies): Official Vaadin scoped package; part of the Vaadin 14 LTS component set. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party @vaadin/cookie-consent at matching version pin; consistent with umbrella package pattern. | ai | |
| phantom-deps | phantom-dep:@vaadin/dashboard | AI (phantom-deps): Aggregator meta-package; deps are re-exported, not directly imported. Same org scope. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Meta/umbrella package by design: tiny payload and minimal README are expected for a dependency aggregator. | ai | |
| phantom-deps | phantom-dep:@vaadin/map | AI (phantom-deps): Umbrella package lists @vaadin/map as a dep for re-export; not directly imported in its own code by design. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 25.1.6 | 8 / 0 | |
| 25.1.5 | 8 / 0 | |
| 25.1.4 | 8 / 0 | |
| 25.1.3 | 8 / 0 | |
| 25.1.2 | 8 / 0 | |
| 25.1.1 | 8 / 0 | |
| 25.1.0 | 8 / 0 | |
| 25.0.11 | 8 / 0 | |
| 25.0.10 | 8 / 0 | |
| 25.0.9 | 8 / 0 | |
| 25.0.8 | 8 / 0 | |
| 25.0.7 | 8 / 0 | |
| 25.0.6 | 8 / 0 | |
| 25.0.5 | 8 / 0 | |
| 25.0.4 | 8 / 0 | |
| 25.0.3 | 8 / 0 | |
| 25.0.2 | 8 / 0 | |
| 25.0.0 | 8 / 0 | |
| 24.10.6 | 9 / 0 | |
| 24.10.4 | 9 / 0 | |
| 24.10.3 | 9 / 0 | |
| 24.10.1 | 9 / 0 | |
| 24.10.0 | 9 / 0 | |
| 24.9.17 | 9 / 0 | |
| 24.9.16 | 9 / 0 | |
| 24.9.14 | 9 / 0 | |
| 24.9.13 | 9 / 0 | |
| 24.9.12 | 9 / 0 | |
| 24.9.11 | 9 / 0 | |
| 24.9.10 | 9 / 0 | |
| 24.9.9 | 9 / 0 | |
| 24.9.8 | 9 / 0 | |
| 24.9.7 | 9 / 0 | |
| 24.9.6 | 9 / 0 | |
| 24.9.5 | 9 / 0 | |
| 24.8.17 | 9 / 0 | |
| 24.8.16 | 9 / 0 | |
| 24.8.15 | 9 / 0 | |
| 24.8.14 | 9 / 0 | |
| 24.8.13 | 9 / 0 | |
| 24.7.15 | 9 / 0 | |
| 24.6.13 | 9 / 0 | |
| 24.5.15 | 8 / 0 | |
| 24.4.23 | 8 / 0 | |
| 24.3.21 | 8 / 0 | |
| 24.2.13 | 8 / 0 | |
| 24.1.18 | 8 / 0 | |
| 24.1.17 | 8 / 0 | |
| 24.0.15 | 8 / 0 | |
| 23.6.10 | 14 / 0 | |
| 23.6.9 | 14 / 0 |
v25.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.8
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.5
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.4
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.16
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.12
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.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.9
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.8.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.14
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.4.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.