@saashub/qoq-eslint-v9-js MIT 21 versions

@saashub/qoq-eslint-v9-js

npm Repository Homepage

Eslint flat config template for JS

21

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

tacgnolladamczyk

Keywords

eslint JavaScript templateflat configsaashubqoqQualityOverQuantity

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:dynamic-require	AI (semgrep): Resolves a fixed relative path (lib/index.cjs); not user-controlled input.	ai	2026/05/16
semgrep	semgrep:child-process-import	AI (semgrep): Used to spawn npx for ESLint inspection tooling; expected pattern for this CLI/config package.	ai	2026/05/16
semgrep	semgrep:child-process-spawn	AI (semgrep): Spawns npx as part of documented inspect tooling; not malicious.	ai	2026/05/16

Versions (showing 21 of 21)

Version	Deps	Published
3.3.0	8 / 7	2026-06-02
3.2.5	8 / 7	2026-05-21
3.2.4	8 / 7	2026-05-16
3.2.3	8 / 7	2026-05-06
3.2.2	8 / 7	2026-04-30
3.2.1	8 / 7	2026-04-17
3.2.0	8 / 7	2026-04-13
3.1.2	8 / 7	2026-04-12
3.1.1	7 / 7	2026-04-03
3.1.0	7 / 7	2026-04-02
3.0.1	7 / 7	2026-03-29
3.0.0	7 / 7	2026-03-25
2.3.0	7 / 7	2026-03-08
2.2.0	7 / 7	2026-02-15
2.1.0	7 / 7	2026-02-05
2.0.4	7 / 7	2026-01-23
2.0.3	7 / 7	2025-12-30
2.0.2	7 / 7	2025-12-15
2.0.1	7 / 7	2025-11-30
2.0.0	7 / 7	2025-11-15
1.12.3	7 / 7	2025-11-11

v3.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.12.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.