@saashub/qoq-eslint-v9-js-vitest
Eslint flat config template for JS + Vitest
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:@vitest/eslint-plugin | AI (dependencies): @vitest/eslint-plugin is the official Vitest ESLint plugin; stable dependency for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads the package's own lib/index.cjs via path.resolve — self-referencing local config, not arbitrary module loading. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; no provenance is consistent across all versions and poses no direct risk. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 3.3.0 | 3 / 4 | |
| 3.2.5 | 3 / 4 | |
| 3.2.2 | 3 / 4 | |
| 3.0.1 | 3 / 5 | |
| 2.0.2 | 3 / 5 | |
| 2.0.1 | 3 / 5 | |
| 2.0.0 | 3 / 5 | |
| 1.12.3 | 3 / 5 |
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.