@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 — 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 |
|---|---|---|---|---|
| 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 75 of 75)
| Version | Deps | Published |
|---|---|---|
| 25.1.6 | 6 / 0 | |
| 25.1.5 | 6 / 0 | |
| 25.1.4 | 6 / 0 | |
| 25.1.3 | 6 / 0 | |
| 25.1.2 | 6 / 0 | |
| 25.1.1 | 6 / 0 | |
| 25.1.0 | 6 / 0 | |
| 25.0.13 | 6 / 0 | |
| 25.0.12 | 6 / 0 | |
| 25.0.11 | 6 / 0 | |
| 25.0.10 | 6 / 0 | |
| 25.0.9 | 6 / 0 | |
| 25.0.8 | 6 / 0 | |
| 25.0.7 | 6 / 0 | |
| 25.0.6 | 6 / 0 | |
| 25.0.5 | 6 / 0 | |
| 25.0.4 | 6 / 0 | |
| 25.0.3 | 6 / 0 | |
| 25.0.2 | 6 / 0 | |
| 25.0.1 | 6 / 0 | |
| 25.0.0 | 6 / 0 | |
| 24.10.5 | 6 / 0 | |
| 24.10.4 | 6 / 0 | |
| 24.10.3 | 6 / 0 | |
| 24.10.2 | 6 / 0 | |
| 24.10.1 | 6 / 0 | |
| 24.10.0 | 6 / 0 | |
| 24.9.18 | 6 / 0 | |
| 24.9.17 | 6 / 0 | |
| 24.9.16 | 6 / 0 | |
| 24.9.15 | 6 / 0 | |
| 24.9.14 | 6 / 0 | |
| 24.9.13 | 6 / 0 | |
| 24.9.12 | 6 / 0 | |
| 24.9.11 | 6 / 0 | |
| 24.9.10 | 6 / 0 | |
| 24.9.9 | 6 / 0 | |
| 24.9.8 | 6 / 0 | |
| 24.9.7 | 6 / 0 | |
| 24.9.6 | 6 / 0 | |
| 24.9.5 | 6 / 0 | |
| 24.9.4 | 6 / 0 | |
| 24.9.3 | 6 / 0 | |
| 24.9.2 | 6 / 0 | |
| 24.9.1 | 6 / 0 | |
| 24.9.0 | 6 / 0 | |
| 24.8.16 | 6 / 0 | |
| 24.8.15 | 6 / 0 | |
| 24.8.14 | 6 / 0 | |
| 24.8.13 | 6 / 0 | |
| 24.8.12 | 6 / 0 | |
| 24.8.11 | 6 / 0 | |
| 24.8.10 | 6 / 0 | |
| 24.8.9 | 6 / 0 | |
| 24.8.8 | 6 / 0 | |
| 24.8.7 | 6 / 0 | |
| 24.8.6 | 6 / 0 | |
| 24.8.5 | 6 / 0 | |
| 24.8.4 | 6 / 0 | |
| 24.8.3 | 6 / 0 | |
| 24.8.2 | 6 / 0 | |
| 24.8.1 | 6 / 0 | |
| 24.8.0 | 6 / 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.6.12 | 8 / 17 | |
| 24.6.11 | 8 / 17 |
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 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 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 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. 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 findingPackage 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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.1
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.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.8.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.9
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.8
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.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.6
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.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.4
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.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.1
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.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.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.11
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.10
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.9
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.8
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.6
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.
v24.7.4
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.3
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.6.12
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.6.11
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.