@vaadin/hilla-generator-plugin-subtypes Apache 2.0 51 versions

@vaadin/hilla-generator-plugin-subtypes

npm Repository Homepage

A Hilla TypeScript Generator plugin to support JsonSubTypes

51

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

web-padawandiegocardosoalvarezguilleplatoshajounimanoloyuriyyevvaadin-ownertomivirkkiartur-sunzhewyqsissbruecker

Keywords

hillatypescriptgenerator

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 org publisher with strong track record; individual maintainer email domain risk is low given org-level controls.	ai	2026/05/10
phantom-deps	phantom-dep:@vaadin/hilla-generator-plugin-model	AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires on transitive/type-only usage patterns common in this package suite.	ai	2026/04/29
phantom-deps	phantom-dep:@vaadin/hilla-generator-plugin-client	AI (phantom-deps): Same-org monorepo dep; same rationale as plugin-model.	ai	2026/04/29
phantom-deps	phantom-dep:openapi-types	AI (phantom-deps): Type-only dependency common in TS generator packages; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:fast-deep-equal	AI (phantom-deps): Utility dep referenced in config/test context; stable false positive for this package.	ai	2026/04/29

Versions (showing 51 of 74)

View all versions

Version	Deps	Published
25.1.5	7 / 0	2026-05-25
25.1.4	7 / 0	2026-05-04
25.1.3	7 / 0	2026-04-27
25.1.2	7 / 0	2026-04-16
25.1.1	7 / 0	2026-03-30
25.1.0	7 / 0	2026-03-24
25.0.13	7 / 0	2026-06-08
25.0.12	7 / 0	2026-05-04
25.0.10	7 / 0	2026-04-27
25.0.9	7 / 0	2026-04-20
25.0.8	7 / 0	2026-03-26
25.0.7	7 / 0	2026-03-10
25.0.6	7 / 0	2026-02-24
25.0.5	7 / 0	2026-02-09
25.0.4	7 / 0	2026-01-27
25.0.3	7 / 0	2026-01-12
25.0.2	7 / 0	2025-12-23
25.0.1	7 / 0	2025-12-22
25.0.0	7 / 0	2025-12-16
24.10.5	7 / 0	2026-05-20
24.10.4	7 / 0	2026-05-04
24.10.3	7 / 0	2026-04-27
24.10.2	7 / 0	2026-04-20
24.10.1	7 / 0	2026-04-02
24.10.0	7 / 0	2026-03-17
24.9.17	7 / 0	2026-05-04
24.9.16	7 / 0	2026-04-27
24.9.15	7 / 0	2026-04-20
24.9.14	7 / 0	2026-03-31
24.9.13	7 / 0	2026-03-10
24.9.12	7 / 0	2026-02-23
24.9.11	7 / 0	2026-02-09
24.9.10	7 / 0	2026-01-28
24.9.9	7 / 0	2026-01-12
24.9.8	7 / 0	2025-12-22
24.9.7	7 / 0	2025-12-11
24.9.6	7 / 0	2025-11-26
24.9.5	7 / 0	2025-11-10
24.9.4	7 / 0	2025-10-29
24.9.3	7 / 0	2025-10-17
24.9.2	7 / 0	2025-10-03
24.9.1	7 / 0	2025-09-29
24.9.0	7 / 0	2025-09-16
24.8.16	7 / 0	2025-12-16
24.8.15	7 / 0	2025-12-11
24.8.14	7 / 0	2025-11-26
24.8.13	7 / 0	2025-11-10
24.8.12	7 / 0	2025-10-29
24.8.11	7 / 0	2025-10-17
24.8.10	7 / 0	2025-10-03
24.8.9	7 / 0	2025-09-29

v25.1.5

1 finding

LOW No provenance attestation provenance

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

v25.1.4

1 finding

LOW No provenance attestation provenance

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

v25.1.3

1 finding

LOW No provenance attestation provenance

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

v25.1.2

1 finding

LOW No provenance attestation provenance

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

v25.1.1

1 finding

LOW No provenance attestation provenance

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

v25.1.0

1 finding

LOW No provenance attestation provenance

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

v25.0.13

1 finding

LOW No provenance attestation provenance

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

v25.0.12

1 finding

LOW No provenance attestation provenance

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

v25.0.10

1 finding

LOW No provenance attestation provenance

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

v25.0.9

1 finding

LOW No provenance attestation provenance

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

v25.0.8

1 finding

LOW No provenance attestation provenance

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

v25.0.7

1 finding

LOW No provenance attestation provenance

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

v25.0.6

1 finding

LOW No provenance attestation provenance

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

v25.0.5

1 finding

LOW No provenance attestation provenance

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

v25.0.4

1 finding

LOW No provenance attestation provenance

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

v25.0.3

1 finding

LOW No provenance attestation provenance

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

v25.0.2

1 finding

LOW No provenance attestation provenance

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

v25.0.1

1 finding

LOW No provenance attestation provenance

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

v25.0.0

1 finding

LOW No provenance attestation provenance

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

v24.10.5

1 finding

LOW No provenance attestation provenance

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

v24.10.4

1 finding

LOW No provenance attestation provenance

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

v24.10.2

1 finding

LOW No provenance attestation provenance

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

v24.10.1

1 finding

LOW No provenance attestation provenance

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

v24.10.0

1 finding

LOW No provenance attestation provenance

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

v24.9.17

1 finding

LOW No provenance attestation provenance

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

v24.9.16

1 finding

LOW No provenance attestation provenance

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

v24.9.15

1 finding

LOW No provenance attestation provenance

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

v24.9.14

1 finding

LOW No provenance attestation provenance

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

v24.9.13

1 finding

LOW No provenance attestation provenance

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

v24.9.12

1 finding

LOW No provenance attestation provenance

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

v24.9.11

1 finding

LOW No provenance attestation provenance

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

v24.9.10

1 finding

LOW No provenance attestation provenance

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

v24.9.9

1 finding

LOW No provenance attestation provenance

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

v24.9.8

1 finding

LOW No provenance attestation provenance

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

v24.9.7

1 finding

LOW No provenance attestation provenance

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

v24.9.6

1 finding

LOW No provenance attestation provenance

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

v24.9.5

1 finding

LOW No provenance attestation provenance

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

v24.9.4

1 finding

LOW No provenance attestation provenance

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

v24.9.3

1 finding

LOW No provenance attestation provenance

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

v24.9.2

2 findings

HIGH Unclaimed maintainer email domain: jouni.me email-domain

Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v24.9.1

2 findings

HIGH Unclaimed maintainer email domain: jouni.me email-domain

Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v24.9.0

2 findings

HIGH Unclaimed maintainer email domain: jouni.me email-domain

Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

v24.8.15

1 finding

LOW No provenance attestation provenance

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

v24.8.14

1 finding

LOW No provenance attestation provenance

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

v24.8.13

1 finding

LOW No provenance attestation provenance

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

v24.8.12

1 finding

LOW No provenance attestation provenance

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

v24.8.11

1 finding

LOW No provenance attestation provenance

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

v24.8.10

2 findings

HIGH Unclaimed maintainer email domain: jouni.me email-domain

Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v24.8.9

2 findings

HIGH Unclaimed maintainer email domain: jouni.me email-domain

Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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