@vaadin/text-field
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Vaadin publishes from a known monorepo; lack of Sigstore provenance is consistent across their entire package ecosystem and is not a risk indicator here. | ai | |
| dependencies | unvetted-dep:lit | AI (dependencies): lit is a widely-used, well-maintained web components library from Google/Polymer; not a risk for this package. | 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/a11y-base | AI (dependencies): Sibling Vaadin monorepo package at matching version pin; expected dependency. | ai | |
| dependencies | unvetted-dep:@vaadin/field-base | AI (dependencies): Sibling Vaadin monorepo package at matching version pin; expected dependency. | ai | |
| dependencies | unvetted-dep:@vaadin/component-base | AI (dependencies): Sibling Vaadin monorepo package at matching version pin; expected dependency. | ai | |
| dependencies | unvetted-dep:@vaadin/input-container | AI (dependencies): Sibling Vaadin monorepo package at matching version pin; expected dependency. | ai | |
| dependencies | unvetted-dep:@vaadin/vaadin-themable-mixin | AI (dependencies): Sibling Vaadin monorepo package at matching version pin; expected dependency. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 25.1.3 | 7 / 6 | |
| 25.1.2 | 7 / 6 | |
| 25.1.1 | 7 / 6 | |
| 25.1.0 | 7 / 6 | |
| 25.0.12 | 7 / 6 | |
| 25.0.11 | 7 / 6 | |
| 25.0.10 | 7 / 6 | |
| 25.0.9 | 7 / 6 | |
| 25.0.8 | 7 / 6 | |
| 25.0.7 | 7 / 6 | |
| 25.0.5 | 7 / 6 | |
| 25.0.4 | 7 / 6 | |
| 25.0.3 | 7 / 6 | |
| 25.0.2 | 7 / 5 | |
| 25.0.1 | 7 / 5 | |
| 25.0.0 | 7 / 5 | |
| 24.10.3 | 10 / 4 | |
| 24.10.2 | 10 / 4 | |
| 24.10.1 | 10 / 4 | |
| 24.10.0 | 10 / 4 | |
| 24.9.15 | 10 / 4 | |
| 24.9.14 | 10 / 4 | |
| 24.9.13 | 10 / 4 | |
| 24.9.12 | 10 / 4 | |
| 24.9.11 | 10 / 4 | |
| 24.9.10 | 10 / 4 | |
| 24.9.9 | 10 / 4 | |
| 24.9.8 | 10 / 4 | |
| 24.9.7 | 10 / 4 | |
| 24.9.6 | 10 / 4 | |
| 24.9.5 | 10 / 4 | |
| 24.9.4 | 10 / 4 | |
| 24.9.3 | 10 / 4 | |
| 24.8.14 | 10 / 4 | |
| 24.8.13 | 10 / 4 | |
| 24.8.12 | 10 / 4 | |
| 24.8.11 | 10 / 4 | |
| 24.8.10 | 10 / 4 | |
| 23.6.4 | 7 / 3 | |
| 23.6.3 | 7 / 3 |
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.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1
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. Consider requesting the maintainer enable provenance via CI/CD.
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.10.0
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.13
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.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.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.
v23.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.