@vaadin/hilla-file-router
Hilla file-based router
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:tsc-template | AI (dependencies): Pinned to 0.2.3; consistent with codegen/build tooling purpose of this file-router package. | ai | |
| email-domain | unclaimed-email:jouni.me | AI (email-domain): Vaadin org package with long track record; individual maintainer email domain lapse is low exploitation risk for this established publisher. | ai | |
| phantom-deps | phantom-dep:@types/chai | AI (phantom-deps): @types/chai is a type-only dev dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:c8 | AI (phantom-deps): c8 is a test coverage tool used in scripts only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:rollup | AI (phantom-deps): rollup is a build tool referenced in build scripts; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Vaadin publishes many packages without provenance; consistent across their ecosystem. | ai | |
| phantom-deps | phantom-dep:@ungap/with-resolvers | AI (phantom-deps): @ungap/with-resolvers is a declared runtime dep; phantom-dep heuristic fires because it may be used transitively or via type-only imports. | ai |
Versions (showing 29 of 129)
| Version | Deps | Published |
|---|---|---|
| 24.5.11 | 6 / 16 | |
| 24.5.10 | 6 / 16 | |
| 24.5.9 | 6 / 16 | |
| 24.5.8 | 6 / 16 | |
| 24.5.7 | 6 / 16 | |
| 24.5.6 | 6 / 16 | |
| 24.5.5 | 6 / 16 | |
| 24.5.4 | 6 / 16 | |
| 24.5.3 | 6 / 16 | |
| 24.5.2 | 6 / 16 | |
| 24.5.1 | 6 / 16 | |
| 24.5.0 | 6 / 16 | |
| 24.4.20 | 5 / 16 | |
| 24.4.19 | 5 / 16 | |
| 24.4.18 | 5 / 16 | |
| 24.4.17 | 5 / 16 | |
| 24.4.16 | 5 / 16 | |
| 24.4.15 | 5 / 16 | |
| 24.4.10 | 5 / 16 | |
| 24.4.9 | 5 / 16 | |
| 24.4.8 | 5 / 16 | |
| 24.4.7 | 5 / 16 | |
| 24.4.6 | 5 / 16 | |
| 24.4.5 | 5 / 16 | |
| 24.4.4 | 5 / 16 | |
| 24.4.3 | 5 / 16 | |
| 24.4.2 | 5 / 16 | |
| 24.4.1 | 5 / 16 | |
| 24.4.0 | 5 / 16 |
v24.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.