eslint-plugin-qunit
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:eslint-plugin-qunit | AI (npm-metadata): Self-referencing file:// devDep is a standard pattern for ESLint plugins testing themselves; stable across versions. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 8.2.6 | 2 / 39 | |
| 8.2.5 | 2 / 39 | |
| 8.2.4 | 2 / 39 | |
| 8.2.3 | 2 / 39 | |
| 8.2.2 | 2 / 39 | |
| 8.2.1 | 2 / 39 | |
| 8.2.0 | 2 / 39 |
v8.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.