@vaadin/hilla-generator-plugin-barrel
A Hilla TypeScript Generator plugin to generate barrel file
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 org package with strong track record; individual maintainer email domain risk is low given org-level trust. | ai | |
| dependencies | unvetted-dep:@vaadin/hilla-generator-core | AI (dependencies): Same-org monorepo sibling dependency; pinned to matching version, not a third-party risk. | ai | |
| dependencies | unvetted-dep:@vaadin/hilla-generator-utils | AI (dependencies): Same-org monorepo sibling dependency; pinned to matching version, not a third-party risk. | ai | |
| dependencies | unvetted-dep:@vaadin/hilla-generator-plugin-backbone | AI (dependencies): Same-org monorepo sibling dependency; pinned to matching version, not a third-party risk. | ai |
Versions (showing 100 of 132)
| Version | Deps | Published |
|---|---|---|
| 25.2.5 | 4 / 0 | |
| 25.2.4 | 4 / 0 | |
| 25.2.2 | 4 / 0 | |
| 25.2.1 | 4 / 0 | |
| 25.2.0 | 4 / 0 | |
| 25.1.8 | 4 / 0 | |
| 25.1.7 | 4 / 0 | |
| 25.1.6 | 4 / 0 | |
| 25.1.5 | 4 / 0 | |
| 25.1.4 | 4 / 0 | |
| 25.1.3 | 4 / 0 | |
| 25.1.2 | 4 / 0 | |
| 25.1.1 | 4 / 0 | |
| 25.1.0 | 4 / 0 | |
| 25.0.13 | 4 / 0 | |
| 25.0.12 | 4 / 0 | |
| 25.0.11 | 4 / 0 | |
| 25.0.10 | 4 / 0 | |
| 25.0.9 | 4 / 0 | |
| 25.0.8 | 4 / 0 | |
| 25.0.7 | 4 / 0 | |
| 25.0.6 | 4 / 0 | |
| 25.0.5 | 4 / 0 | |
| 25.0.4 | 4 / 0 | |
| 25.0.3 | 4 / 0 | |
| 25.0.2 | 4 / 0 | |
| 25.0.1 | 4 / 0 | |
| 25.0.0 | 4 / 0 | |
| 24.10.7 | 4 / 0 | |
| 24.10.6 | 4 / 0 | |
| 24.10.5 | 4 / 0 | |
| 24.10.4 | 4 / 0 | |
| 24.10.3 | 4 / 0 | |
| 24.10.2 | 4 / 0 | |
| 24.10.1 | 4 / 0 | |
| 24.10.0 | 4 / 0 | |
| 24.9.20 | 4 / 0 | |
| 24.9.19 | 4 / 0 | |
| 24.9.18 | 4 / 0 | |
| 24.9.17 | 4 / 0 | |
| 24.9.16 | 4 / 0 | |
| 24.9.15 | 4 / 0 | |
| 24.9.14 | 4 / 0 | |
| 24.9.13 | 4 / 0 | |
| 24.9.12 | 4 / 0 | |
| 24.9.11 | 4 / 0 | |
| 24.9.10 | 4 / 0 | |
| 24.9.9 | 4 / 0 | |
| 24.9.8 | 4 / 0 | |
| 24.9.7 | 4 / 0 | |
| 24.9.6 | 4 / 0 | |
| 24.9.5 | 4 / 0 | |
| 24.9.4 | 4 / 0 | |
| 24.9.3 | 4 / 0 | |
| 24.9.2 | 4 / 0 | |
| 24.9.1 | 4 / 0 | |
| 24.9.0 | 4 / 0 | |
| 24.8.16 | 4 / 0 | |
| 24.8.15 | 4 / 0 | |
| 24.8.14 | 4 / 0 | |
| 24.8.13 | 4 / 0 | |
| 24.8.12 | 4 / 0 | |
| 24.8.11 | 4 / 0 | |
| 24.8.10 | 4 / 0 | |
| 24.8.9 | 4 / 0 | |
| 24.8.8 | 4 / 0 | |
| 24.8.7 | 4 / 0 | |
| 24.8.6 | 4 / 0 | |
| 24.8.5 | 4 / 0 | |
| 24.8.4 | 4 / 0 | |
| 24.8.3 | 4 / 0 | |
| 24.8.2 | 4 / 0 | |
| 24.8.1 | 4 / 0 | |
| 24.8.0 | 4 / 0 | |
| 24.7.14 | 4 / 0 | |
| 24.7.11 | 4 / 0 | |
| 24.7.10 | 4 / 0 | |
| 24.7.9 | 4 / 0 | |
| 24.7.8 | 4 / 0 | |
| 24.7.7 | 4 / 0 | |
| 24.7.6 | 4 / 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 / 17 | |
| 24.6.11 | 4 / 17 | |
| 24.6.10 | 4 / 17 | |
| 24.6.9 | 4 / 17 | |
| 24.6.8 | 4 / 17 | |
| 24.6.7 | 4 / 17 | |
| 24.6.6 | 4 / 17 | |
| 24.6.5 | 4 / 17 | |
| 24.6.4 | 4 / 17 | |
| 24.6.3 | 4 / 17 | |
| 24.6.2 | 4 / 17 | |
| 24.6.1 | 4 / 17 | |
| 24.6.0 | 4 / 17 |
v25.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.