@qlik/eslint-config
Qlik's ESLint configs
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@vitest/eslint-plugin | AI (dependencies): Legitimate vitest ESLint plugin; consistent with this package's role as an ESLint config collection. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-typescript | AI (phantom-deps): ESLint config packages reference resolvers in config objects, not via direct imports; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/utils | AI (phantom-deps): ESLint config package; deps are referenced in config objects, not imported directly. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-node | AI (phantom-deps): Resolver plugins are referenced by string in ESLint config, not imported. Stable FP for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.0.6 | 12 / 2 | |
| 2.0.4 | 12 / 2 | |
| 2.0.3 | 12 / 2 | |
| 1.4.30 | 19 / 9 | |
| 1.4.29 | 19 / 9 | |
| 1.4.28 | 19 / 9 | |
| 1.4.8 | 18 / 9 |
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.