@saashub/qoq-cli
CLI that handles formatting, linting and testing Your JS/TS code
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:cac | AI (phantom-deps): Rollup-bundled CLI; deps are declared but bundled, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Rollup-bundled CLI; deps are declared but bundled, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): Rollup-bundled CLI; deps are declared but bundled, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:es-toolkit | AI (phantom-deps): Rollup-bundled CLI; deps are declared but bundled, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:micromatch | AI (phantom-deps): Rollup-bundled CLI; deps are declared but bundled, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:picocolors | AI (phantom-deps): Rollup-bundled CLI; deps are declared but bundled, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:cosmiconfig | AI (phantom-deps): Rollup-bundled CLI; deps are declared but bundled, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@eslint/compat | AI (phantom-deps): Rollup-bundled CLI; deps are declared but bundled, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@antfu/install-pkg | AI (phantom-deps): Rollup-bundled CLI; deps are declared but bundled, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@saashub/qoq-utils | AI (phantom-deps): Same org scope; rollup-bundled CLI pattern makes direct imports invisible to static analysis. | ai | |
| phantom-deps | phantom-dep:react-fast-compare | AI (phantom-deps): Rollup-bundled CLI; deps are declared but bundled, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@npmcli/package-json | AI (phantom-deps): Rollup-bundled CLI; deps are declared but bundled, not directly imported in source. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 3.3.0 | 12 / 12 | |
| 3.2.5 | 12 / 12 | |
| 3.2.4 | 12 / 12 | |
| 3.2.3 | 12 / 12 | |
| 3.2.2 | 12 / 12 | |
| 3.2.1 | 12 / 12 | |
| 3.2.0 | 12 / 12 | |
| 3.1.2 | 12 / 12 | |
| 3.1.1 | 12 / 13 | |
| 3.1.0 | 12 / 13 | |
| 3.0.1 | 12 / 13 | |
| 3.0.0 | 12 / 13 | |
| 2.3.0 | 12 / 14 | |
| 2.2.0 | 12 / 14 | |
| 2.1.0 | 12 / 14 | |
| 2.0.4 | 11 / 13 | |
| 2.0.3 | 11 / 13 | |
| 2.0.2 | 11 / 13 | |
| 2.0.1 | 11 / 13 | |
| 2.0.0 | 11 / 13 | |
| 1.12.3 | 11 / 13 |
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage 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.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.