← Home

@vaadin/hilla-react-crud

Hilla CRUD utils for React

100
Versions
Apache-2.0
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

HillaCRUDReact

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
email-domain unclaimed-email:jouni.me AI (email-domain): Vaadin-owned package with strong org identity; individual maintainer email domain risk is low in this context. ai
dependencies unvetted-dep:@vaadin/react-components AI (dependencies): First-party Vaadin component library; stable dependency across all Vaadin/Hilla package versions. ai
provenance no-provenance AI (provenance): Vaadin publishes without Sigstore provenance consistently; stable false positive for this package. ai

Versions (showing 100 of 131)

Version Deps Published
25.2.5 6 / 0
25.2.4 6 / 0
25.2.2 6 / 0
25.2.1 6 / 0
25.2.0 6 / 0
25.1.8 6 / 0
25.1.7 6 / 0
25.1.6 6 / 0
25.1.5 6 / 0
25.1.4 6 / 0
25.1.3 6 / 0
25.1.2 6 / 0
25.1.1 6 / 0
25.1.0 6 / 0
25.0.13 6 / 0
25.0.12 6 / 0
25.0.10 6 / 0
25.0.9 6 / 0
25.0.8 6 / 0
25.0.7 6 / 0
25.0.6 6 / 0
25.0.5 6 / 0
25.0.4 6 / 0
25.0.3 6 / 0
25.0.2 6 / 0
25.0.1 6 / 0
25.0.0 6 / 0
24.10.7 6 / 0
24.10.6 6 / 0
24.10.5 6 / 0
24.10.4 6 / 0
24.10.3 6 / 0
24.10.2 6 / 0
24.10.1 6 / 0
24.10.0 6 / 0
24.9.20 6 / 0
24.9.19 6 / 0
24.9.18 6 / 0
24.9.17 6 / 0
24.9.16 6 / 0
24.9.15 6 / 0
24.9.14 6 / 0
24.9.13 6 / 0
24.9.12 6 / 0
24.9.11 6 / 0
24.9.10 6 / 0
24.9.9 6 / 0
24.9.8 6 / 0
24.9.7 6 / 0
24.9.6 6 / 0
24.9.5 6 / 0
24.9.4 6 / 0
24.9.3 6 / 0
24.9.2 6 / 0
24.9.1 6 / 0
24.9.0 6 / 0
24.8.16 6 / 0
24.8.15 6 / 0
24.8.14 6 / 0
24.8.13 6 / 0
24.8.12 6 / 0
24.8.11 6 / 0
24.8.10 6 / 0
24.8.9 6 / 0
24.8.8 6 / 0
24.8.7 6 / 0
24.8.6 6 / 0
24.8.5 6 / 0
24.8.4 6 / 0
24.8.3 6 / 0
24.8.2 6 / 0
24.8.1 6 / 0
24.8.0 6 / 0
24.7.14 5 / 0
24.7.11 5 / 0
24.7.10 5 / 0
24.7.9 5 / 0
24.7.8 5 / 0
24.7.7 5 / 0
24.7.6 5 / 0
24.7.5 4 / 0
24.7.4 4 / 0
24.7.3 4 / 0
24.7.2 4 / 0
24.7.1 4 / 0
24.7.0 4 / 0
24.6.12 4 / 19
24.6.11 4 / 19
24.6.10 4 / 19
24.6.9 4 / 19
24.6.8 4 / 19
24.6.7 4 / 19
24.6.6 4 / 19
24.6.5 4 / 19
24.6.4 4 / 19
24.6.3 4 / 19
24.6.2 4 / 19
24.6.1 4 / 19
24.6.0 4 / 18
24.5.14 4 / 18
Showing 100 of 131 Next page →

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.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.2.0

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.

v24.10.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.

v24.9.20

1 finding
INFO No provenance attestation provenance

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

v24.9.19

1 finding
INFO No provenance attestation provenance

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

v24.7.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.7.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.7.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.6.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.6.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.6.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.6.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.6.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.6.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.6.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.6.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.6.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v24.5.14

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.