@vaadin/hilla-react-signals
Signals for Hilla React
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:jouni.me | AI (email-domain): Vaadin is a well-known vendor; the jouni.me domain risk is theoretical and not an active threat for this established package. | ai | |
| provenance | no-provenance | AI (provenance): Vaadin publishes without Sigstore provenance consistently; stable false positive for this package family. | ai |
Versions (showing 51 of 130)
| Version | Deps | Published |
|---|---|---|
| 25.2.5 | 3 / 0 | |
| 25.2.4 | 3 / 0 | |
| 25.2.2 | 3 / 0 | |
| 25.2.1 | 3 / 0 | |
| 25.2.0 | 3 / 0 | |
| 25.1.7 | 3 / 0 | |
| 25.1.6 | 3 / 0 | |
| 25.1.5 | 3 / 0 | |
| 25.1.4 | 3 / 0 | |
| 25.1.3 | 3 / 0 | |
| 25.1.2 | 3 / 0 | |
| 25.1.1 | 3 / 0 | |
| 25.1.0 | 3 / 0 | |
| 25.0.13 | 3 / 0 | |
| 25.0.12 | 3 / 0 | |
| 25.0.10 | 3 / 0 | |
| 25.0.9 | 3 / 0 | |
| 25.0.8 | 3 / 0 | |
| 25.0.7 | 3 / 0 | |
| 25.0.6 | 3 / 0 | |
| 25.0.5 | 3 / 0 | |
| 25.0.4 | 3 / 0 | |
| 25.0.3 | 3 / 0 | |
| 25.0.2 | 3 / 0 | |
| 25.0.1 | 3 / 0 | |
| 25.0.0 | 3 / 0 | |
| 24.10.7 | 3 / 0 | |
| 24.10.6 | 3 / 0 | |
| 24.10.5 | 3 / 0 | |
| 24.10.4 | 3 / 0 | |
| 24.10.3 | 3 / 0 | |
| 24.10.2 | 3 / 0 | |
| 24.10.1 | 3 / 0 | |
| 24.10.0 | 3 / 0 | |
| 24.9.20 | 3 / 0 | |
| 24.9.19 | 3 / 0 | |
| 24.9.18 | 3 / 0 | |
| 24.9.17 | 3 / 0 | |
| 24.9.16 | 3 / 0 | |
| 24.9.15 | 3 / 0 | |
| 24.9.14 | 3 / 0 | |
| 24.9.13 | 3 / 0 | |
| 24.9.12 | 3 / 0 | |
| 24.9.11 | 3 / 0 | |
| 24.9.10 | 3 / 0 | |
| 24.9.9 | 3 / 0 | |
| 24.9.8 | 3 / 0 | |
| 24.9.7 | 3 / 0 | |
| 24.9.6 | 3 / 0 | |
| 24.9.5 | 3 / 0 | |
| 24.9.4 | 3 / 0 |
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.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.
v24.10.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.