@vaadin/grid-pro
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 | dormant-publish | AI (publish-pattern): Vaadin publishes versioned backport branches (24.x); dormancy between major series releases is expected, not a takeover signal. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Added deps are canonical Vaadin/Polymer packages consistent with the 24.x Polymer-based series vs 25.x. | ai | |
| phantom-deps | phantom-dep:@polymer/polymer | AI (phantom-deps): @polymer/polymer is a peer/config-level dep in Vaadin 24.x Polymer-based components; not directly imported in JS but legitimately declared. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 25.1.3 | 10 / 6 | |
| 25.1.2 | 10 / 6 | |
| 25.1.1 | 10 / 6 | |
| 25.1.0 | 10 / 6 | |
| 25.0.12 | 9 / 6 | |
| 25.0.11 | 9 / 6 | |
| 25.0.10 | 9 / 6 | |
| 25.0.9 | 9 / 6 | |
| 25.0.8 | 9 / 6 | |
| 25.0.7 | 9 / 6 | |
| 25.0.5 | 9 / 6 | |
| 25.0.4 | 9 / 6 | |
| 25.0.3 | 9 / 6 | |
| 25.0.2 | 9 / 5 | |
| 25.0.1 | 9 / 5 | |
| 25.0.0 | 9 / 5 | |
| 24.10.3 | 12 / 4 | |
| 24.10.2 | 12 / 4 | |
| 24.10.1 | 12 / 4 | |
| 24.10.0 | 12 / 4 | |
| 24.9.15 | 12 / 4 | |
| 24.9.14 | 12 / 4 | |
| 24.9.13 | 12 / 4 | |
| 24.9.12 | 12 / 4 | |
| 24.9.11 | 12 / 4 | |
| 24.9.10 | 12 / 4 | |
| 24.9.9 | 12 / 4 | |
| 24.9.8 | 12 / 4 | |
| 24.9.7 | 12 / 4 | |
| 24.9.6 | 12 / 4 | |
| 24.9.5 | 12 / 4 | |
| 24.8.14 | 12 / 4 | |
| 24.8.13 | 12 / 4 | |
| 24.8.12 | 12 / 4 | |
| 23.6.4 | 13 / 5 | |
| 23.6.3 | 13 / 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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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.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.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.1
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. 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.10.0
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.12
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.