eslint-plugin-qwik
An Open-Source sub-framework designed with a focus on server-side-rendering, lazy-loading, and styling/animation.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:jsx-ast-utils | AI (phantom-deps): jsx-ast-utils is a declared runtime dependency used indirectly via ESLint plugin config files; this is a stable false positive for this package. | ai |
Versions (showing 62 of 162)
| Version | Deps | Published |
|---|---|---|
| 0.13.0 | 0 / 0 | |
| 0.12.1 | 0 / 0 | |
| 0.12.0 | 0 / 0 | |
| 0.11.1 | 0 / 0 | |
| 0.11.0 | 0 / 0 | |
| 0.10.0 | 0 / 0 | |
| 0.9.0 | 0 / 0 | |
| 0.0.113 | 0 / 0 | |
| 0.0.112 | 0 / 0 | |
| 0.0.110 | 0 / 0 | |
| 0.0.109 | 0 / 0 | |
| 0.0.108 | 0 / 0 | |
| 0.0.107 | 0 / 0 | |
| 0.0.106 | 0 / 0 | |
| 0.0.105 | 0 / 0 | |
| 0.0.104 | 0 / 0 | |
| 0.0.103 | 0 / 0 | |
| 0.0.102 | 0 / 0 | |
| 0.0.101 | 0 / 0 | |
| 0.0.100 | 0 / 0 | |
| 0.0.42 | 0 / 0 | |
| 0.0.41 | 0 / 0 | |
| 0.0.40 | 0 / 0 | |
| 0.0.39 | 0 / 0 | |
| 0.0.38 | 0 / 0 | |
| 0.0.37 | 0 / 0 | |
| 0.0.36 | 0 / 0 | |
| 0.0.35 | 0 / 0 | |
| 0.0.34 | 0 / 0 | |
| 0.0.33 | 0 / 0 | |
| 0.0.32 | 0 / 0 | |
| 0.0.31 | 0 / 0 | |
| 0.0.30 | 0 / 0 | |
| 0.0.29 | 0 / 0 | |
| 0.0.28 | 0 / 0 | |
| 0.0.27 | 0 / 0 | |
| 0.0.26 | 0 / 0 | |
| 0.0.25 | 0 / 0 | |
| 0.0.24 | 0 / 0 | |
| 0.0.23 | 0 / 0 | |
| 0.0.22 | 0 / 0 | |
| 0.0.21 | 0 / 0 | |
| 0.0.20 | 0 / 0 | |
| 0.0.18 | 0 / 0 | |
| 2.0.0-beta.32 | 2 / 5 | |
| 2.0.0-beta.31 | 2 / 5 | |
| 2.0.0-beta.30 | 2 / 5 | |
| 2.0.0-beta.29 | 2 / 5 | |
| 2.0.0-beta.28 | 2 / 5 | |
| 2.0.0-beta.27 | 2 / 5 | |
| 2.0.0-beta.26 | 2 / 5 | |
| 2.0.0-beta.25 | 2 / 5 | |
| 2.0.0-beta.24 | 2 / 5 | |
| 2.0.0-beta.23 | 2 / 5 | |
| 2.0.0-beta.21 | 2 / 5 | |
| 2.0.0-beta.19 | 2 / 5 | |
| 2.0.0-beta.18 | 2 / 5 | |
| 2.0.0-beta.17 | 2 / 5 | |
| 2.0.0-beta.16 | 2 / 5 | |
| 2.0.0-beta.15 | 2 / 5 | |
| 2.0.0-beta.14 | 2 / 5 | |
| 2.0.0-beta.13 | 2 / 5 |
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.