@vaadin/vaadin-themable-mixin
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:style-observer | AI (dependencies): style-observer is a purposeful addition to a themable mixin; low-risk CSS utility with no malware indicators. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): style-observer is a legitimate CSS observer utility added as part of a documented Vaadin component refactor. | ai | |
| provenance | no-provenance | AI (provenance): Vaadin packages are published without Sigstore provenance; this is consistent across their entire catalog and not a risk signal for this publisher. | ai | |
| dependencies | unvetted-dep:lit | AI (dependencies): lit is Google's official Lit web components library; a standard and expected dependency for Vaadin web component packages. | ai | |
| dependencies | unvetted-dep:@vaadin/component-base | AI (dependencies): @vaadin/component-base is a sibling package in the Vaadin monorepo; always a legitimate dependency for Vaadin component packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Vaadin monorepo packages often have minimal READMEs; this is a known utility mixin package, not spam. | ai |
Versions (showing 51 of 58)
| Version | Deps | Published |
|---|---|---|
| 25.2.6 | 3 / 5 | |
| 25.2.5 | 3 / 5 | |
| 25.2.4 | 3 / 5 | |
| 25.2.3 | 3 / 5 | |
| 25.2.2 | 3 / 5 | |
| 25.2.1 | 3 / 5 | |
| 25.2.0 | 3 / 5 | |
| 25.1.9 | 3 / 5 | |
| 25.1.8 | 3 / 5 | |
| 25.1.7 | 3 / 5 | |
| 25.1.6 | 3 / 5 | |
| 25.1.5 | 3 / 5 | |
| 25.1.4 | 3 / 5 | |
| 25.1.3 | 3 / 5 | |
| 25.1.2 | 3 / 5 | |
| 25.1.1 | 3 / 5 | |
| 25.1.0 | 3 / 5 | |
| 25.0.13 | 3 / 5 | |
| 25.0.12 | 3 / 5 | |
| 25.0.11 | 3 / 5 | |
| 25.0.10 | 3 / 5 | |
| 25.0.9 | 3 / 5 | |
| 25.0.8 | 3 / 5 | |
| 25.0.7 | 3 / 5 | |
| 25.0.6 | 3 / 5 | |
| 25.0.5 | 3 / 5 | |
| 25.0.4 | 3 / 5 | |
| 25.0.3 | 3 / 5 | |
| 25.0.2 | 3 / 5 | |
| 25.0.1 | 3 / 5 | |
| 25.0.0 | 3 / 5 | |
| 24.10.4 | 3 / 5 | |
| 24.10.3 | 3 / 5 | |
| 24.10.2 | 3 / 5 | |
| 24.10.1 | 3 / 5 | |
| 24.10.0 | 3 / 5 | |
| 24.9.17 | 2 / 5 | |
| 24.9.16 | 3 / 5 | |
| 24.9.15 | 3 / 5 | |
| 24.9.14 | 3 / 5 | |
| 24.9.13 | 3 / 5 | |
| 24.9.12 | 3 / 5 | |
| 24.9.11 | 3 / 5 | |
| 24.9.10 | 3 / 5 | |
| 24.9.9 | 3 / 5 | |
| 24.9.8 | 3 / 5 | |
| 24.9.7 | 3 / 5 | |
| 24.9.6 | 3 / 5 | |
| 24.9.5 | 3 / 5 | |
| 24.9.4 | 3 / 5 | |
| 24.9.3 | 3 / 5 |
v25.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.6
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. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.