← Home

@vaadin/combo-box

51
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

web-padawandiegocardosoalvarezguilleplatoshajounimanoloyuriyyevvaadin-ownertomivirkkiartur-sunzhewyqsissbruecker

Keywords

Vaadincombo-boxweb-componentsweb-component

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Vaadin publishes without Sigstore provenance consistently; stable false positive for this package family. ai

Versions (showing 51 of 53)

View all versions
Version Deps Published
25.2.6 10 / 6
25.2.5 10 / 6
25.2.4 10 / 6
25.2.3 10 / 6
25.2.2 10 / 6
25.2.1 10 / 6
25.2.0 10 / 6
25.1.9 10 / 6
25.1.8 10 / 6
25.1.7 10 / 6
25.1.6 10 / 6
25.1.5 10 / 6
25.1.4 10 / 6
25.1.3 10 / 6
25.1.2 10 / 6
25.1.1 10 / 6
25.1.0 10 / 6
25.0.13 10 / 6
25.0.12 10 / 6
25.0.11 10 / 6
25.0.10 10 / 6
25.0.9 10 / 6
25.0.8 10 / 6
25.0.7 10 / 6
25.0.5 10 / 6
25.0.4 10 / 6
25.0.3 10 / 6
25.0.2 10 / 5
25.0.1 10 / 5
25.0.0 10 / 5
24.10.4 13 / 5
24.10.3 13 / 5
24.10.2 13 / 5
24.10.1 13 / 5
24.10.0 13 / 5
24.9.17 13 / 5
24.9.16 13 / 5
24.9.15 13 / 5
24.9.14 13 / 5
24.9.13 13 / 5
24.9.12 13 / 5
24.9.11 13 / 5
24.9.10 13 / 5
24.9.9 13 / 5
24.9.8 13 / 5
24.9.7 13 / 5
24.9.6 13 / 5
24.9.5 13 / 5
24.8.14 13 / 5
24.8.13 13 / 5
24.8.12 13 / 5

v25.2.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.2.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.2.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.2.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.2.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.2.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.1.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.1.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.1.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.1.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.