@vaadin/a11y-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 a well-established Google-maintained web components library; its use is expected and appropriate for Vaadin web component packages. | ai | |
| provenance | no-provenance | AI (provenance): Vaadin is an established vendor with a long publishing history; lack of Sigstore provenance is common and not a risk indicator for this package. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 25.1.3 | 3 / 4 | |
| 25.1.2 | 3 / 4 | |
| 25.1.1 | 3 / 4 | |
| 25.1.0 | 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.6 | 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 / 4 | |
| 25.0.0 | 3 / 4 | |
| 24.10.3 | 4 / 4 | |
| 24.10.2 | 4 / 4 | |
| 24.10.1 | 4 / 4 | |
| 24.10.0 | 4 / 4 | |
| 24.9.15 | 4 / 4 | |
| 24.9.14 | 4 / 4 | |
| 24.9.13 | 4 / 4 | |
| 24.9.12 | 4 / 4 | |
| 24.9.11 | 4 / 4 | |
| 24.9.10 | 4 / 4 | |
| 24.9.9 | 4 / 4 | |
| 24.9.8 | 4 / 4 | |
| 24.9.7 | 4 / 4 | |
| 24.9.6 | 4 / 4 | |
| 24.9.5 | 4 / 4 | |
| 24.9.4 | 4 / 4 | |
| 24.9.3 | 4 / 4 | |
| 24.8.14 | 4 / 4 | |
| 24.8.13 | 4 / 4 | |
| 24.8.12 | 4 / 4 | |
| 24.8.11 | 4 / 4 | |
| 24.8.10 | 4 / 4 |
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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 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
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.