@vaadin/hilla-generator-plugin-signals
A Hilla TypeScript Generator plugin to add Shared Signals support
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 many packages without provenance; consistent across their ecosystem. | ai | |
| phantom-deps | phantom-dep:@vaadin/hilla-generator-plugin-client | AI (phantom-deps): Same-org monorepo sibling dependency; not a phantom dep concern. | ai | |
| phantom-deps | phantom-dep:@vaadin/hilla-generator-plugin-backbone | AI (phantom-deps): Same-org monorepo sibling dependency; not a phantom dep concern. | ai | |
| dependencies | unvetted-dep:iterator-helpers-polyfill | AI (dependencies): Pinned polyfill dep; expected for a TS generator plugin targeting Node >=16. | ai | |
| dependencies | unvetted-dep:tsc-template | AI (dependencies): Pinned utility dep for TS code generation; consistent with this plugin's documented purpose across versions. | ai | |
| phantom-deps | phantom-dep:openapi-types | AI (phantom-deps): openapi-types is a type-only dep used in TS config/type declarations; not directly imported at runtime is expected. | ai | |
| phantom-deps | phantom-dep:fast-deep-equal | AI (phantom-deps): Likely used indirectly via compiled output; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 51 of 59)
| Version | Deps | Published |
|---|---|---|
| 25.1.6 | 7 / 3 | |
| 25.1.5 | 7 / 3 | |
| 25.1.4 | 7 / 3 | |
| 25.1.3 | 7 / 3 | |
| 25.1.2 | 7 / 3 | |
| 25.1.1 | 7 / 3 | |
| 25.1.0 | 7 / 3 | |
| 25.0.13 | 7 / 3 | |
| 25.0.12 | 7 / 3 | |
| 25.0.11 | 7 / 3 | |
| 25.0.10 | 7 / 3 | |
| 25.0.9 | 7 / 3 | |
| 25.0.8 | 7 / 3 | |
| 25.0.7 | 7 / 3 | |
| 25.0.6 | 7 / 3 | |
| 25.0.5 | 7 / 3 | |
| 25.0.4 | 7 / 3 | |
| 25.0.3 | 7 / 3 | |
| 25.0.2 | 7 / 3 | |
| 25.0.1 | 7 / 3 | |
| 25.0.0 | 7 / 3 | |
| 24.10.6 | 7 / 3 | |
| 24.10.5 | 7 / 3 | |
| 24.10.4 | 7 / 3 | |
| 24.10.3 | 7 / 3 | |
| 24.10.2 | 7 / 3 | |
| 24.10.1 | 7 / 3 | |
| 24.10.0 | 7 / 3 | |
| 24.9.18 | 7 / 3 | |
| 24.9.17 | 7 / 3 | |
| 24.9.16 | 7 / 3 | |
| 24.9.15 | 7 / 3 | |
| 24.9.14 | 7 / 3 | |
| 24.9.13 | 7 / 3 | |
| 24.9.12 | 7 / 3 | |
| 24.9.11 | 7 / 3 | |
| 24.9.10 | 7 / 3 | |
| 24.9.9 | 7 / 3 | |
| 24.9.8 | 7 / 3 | |
| 24.9.7 | 7 / 3 | |
| 24.9.6 | 7 / 3 | |
| 24.9.5 | 7 / 3 | |
| 24.9.4 | 7 / 3 | |
| 24.9.3 | 7 / 3 | |
| 24.9.2 | 7 / 3 | |
| 24.8.16 | 7 / 3 | |
| 24.8.15 | 7 / 3 | |
| 24.8.14 | 7 / 3 | |
| 24.8.13 | 7 / 3 | |
| 24.8.12 | 7 / 3 | |
| 24.8.11 | 7 / 3 |
v25.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.13
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. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.10
1 findingPackage 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.6
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.2
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.10.6
1 finding[Accepted risk] Package 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.18
1 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.6
1 finding[Accepted risk] Package 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.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.8.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.