@vaadin/hilla-generator-core
A Hilla tool to generate TypeScript code from the OpenAPI document
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 org package; no provenance is consistent across their entire published portfolio. | ai | |
| phantom-deps | phantom-dep:meow | AI (phantom-deps): meow is explicitly declared in dependencies; phantom-dep is a false positive for this package. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 25.1.5 | 5 / 0 | |
| 25.1.4 | 5 / 0 | |
| 25.1.3 | 5 / 0 | |
| 25.1.2 | 5 / 0 | |
| 25.1.1 | 5 / 0 | |
| 25.1.0 | 5 / 0 | |
| 25.0.12 | 5 / 0 | |
| 25.0.11 | 5 / 0 | |
| 25.0.10 | 5 / 0 | |
| 25.0.9 | 5 / 0 | |
| 25.0.8 | 5 / 0 | |
| 25.0.7 | 5 / 0 | |
| 25.0.6 | 5 / 0 | |
| 25.0.5 | 5 / 0 | |
| 25.0.4 | 5 / 0 | |
| 25.0.3 | 5 / 0 | |
| 25.0.2 | 5 / 0 | |
| 25.0.1 | 5 / 0 | |
| 25.0.0 | 5 / 0 | |
| 24.10.5 | 5 / 0 | |
| 24.10.4 | 5 / 0 | |
| 24.10.3 | 5 / 0 | |
| 24.10.2 | 5 / 0 | |
| 24.10.1 | 5 / 0 | |
| 24.10.0 | 5 / 0 | |
| 24.9.17 | 5 / 0 | |
| 24.9.16 | 5 / 0 | |
| 24.9.15 | 5 / 0 | |
| 24.9.14 | 5 / 0 | |
| 24.9.13 | 5 / 0 | |
| 24.9.12 | 5 / 0 | |
| 24.9.11 | 5 / 0 | |
| 24.9.10 | 5 / 0 | |
| 24.9.9 | 5 / 0 | |
| 24.9.8 | 5 / 0 | |
| 24.9.7 | 5 / 0 | |
| 24.9.6 | 5 / 0 | |
| 24.9.5 | 5 / 0 | |
| 24.9.4 | 5 / 0 | |
| 24.9.3 | 5 / 0 | |
| 24.8.16 | 5 / 0 | |
| 24.8.15 | 5 / 0 | |
| 24.8.14 | 5 / 0 | |
| 24.8.13 | 5 / 0 | |
| 24.8.12 | 5 / 0 | |
| 24.8.11 | 5 / 0 | |
| 24.8.5 | 5 / 0 | |
| 24.8.2 | 5 / 0 | |
| 24.7.14 | 5 / 0 | |
| 24.7.7 | 5 / 0 | |
| 24.7.5 | 5 / 0 |
v25.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.1.0
1 findingPackage 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. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.9.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.5
2 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.2
2 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.7.14
2 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.7.7
2 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.7.5
2 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.