@vaadin/grid
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps (@polymer/polymer, @vaadin/vaadin-lumo-styles, @vaadin/vaadin-material-styles, @vaadin/a11y-base, lit) are established, legitimate packages in the Vaadin/Polymer/Lit ecosystem. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Major version bump (23.x to 24.x) naturally introduces many new source files; no obfuscation or suspicious patterns flagged. | ai | |
| dependencies | unvetted-dep:@open-wc/dedupe-mixin | AI (dependencies): @open-wc/dedupe-mixin is a standard open-wc utility; legitimate and expected dependency for web component packages. | ai | |
| dependencies | unvetted-dep:@vaadin/checkbox | AI (dependencies): First-party @vaadin/* sibling package from the same monorepo release; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:@vaadin/a11y-base | AI (dependencies): First-party @vaadin/* sibling package from the same monorepo release; expected dependency pattern. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): @vaadin/grid is a scoped Vaadin data grid component with no meaningful similarity to 'uuid'; the levenshtein match is a false positive that generalizes across all versions. | ai | |
| dependencies | unvetted-dep:@vaadin/lit-renderer | AI (dependencies): First-party @vaadin/* sibling package from the same monorepo release; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:@vaadin/component-base | AI (dependencies): First-party @vaadin/* sibling package from the same monorepo release; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:@vaadin/vaadin-themable-mixin | AI (dependencies): First-party @vaadin/* sibling package from the same monorepo release; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:@vaadin/text-field | AI (dependencies): First-party @vaadin/* sibling package from the same monorepo release; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:lit | AI (dependencies): 'lit' is a well-known Google/Polymer web components library; a standard dependency for Vaadin components. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 25.1.3 | 8 / 6 | |
| 25.1.2 | 8 / 6 | |
| 25.1.1 | 8 / 6 | |
| 25.1.0 | 8 / 6 | |
| 25.0.12 | 8 / 6 | |
| 25.0.11 | 8 / 6 | |
| 25.0.10 | 8 / 6 | |
| 25.0.9 | 8 / 6 | |
| 25.0.8 | 8 / 6 | |
| 25.0.7 | 8 / 6 | |
| 25.0.5 | 8 / 6 | |
| 25.0.4 | 8 / 6 | |
| 25.0.3 | 8 / 6 | |
| 25.0.2 | 8 / 5 | |
| 25.0.1 | 8 / 5 | |
| 25.0.0 | 8 / 5 | |
| 24.10.3 | 11 / 4 | |
| 24.10.2 | 11 / 4 | |
| 24.10.1 | 11 / 4 | |
| 24.10.0 | 11 / 4 | |
| 24.9.15 | 11 / 4 | |
| 24.9.14 | 11 / 4 | |
| 24.9.13 | 11 / 4 | |
| 24.9.12 | 11 / 4 | |
| 24.9.11 | 11 / 4 | |
| 24.9.10 | 11 / 4 | |
| 24.9.9 | 11 / 4 | |
| 24.9.8 | 11 / 4 | |
| 24.9.7 | 11 / 4 | |
| 24.9.6 | 11 / 4 | |
| 24.9.5 | 11 / 4 | |
| 24.9.4 | 11 / 4 | |
| 24.9.3 | 11 / 4 | |
| 24.8.14 | 11 / 4 | |
| 24.8.13 | 11 / 4 | |
| 24.8.12 | 11 / 4 | |
| 24.8.11 | 11 / 4 | |
| 24.8.10 | 11 / 4 | |
| 23.6.4 | 9 / 5 | |
| 23.6.3 | 9 / 5 |
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.3
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.