@qoder-ai/qodercli
qodercli - npm installer
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-execsync | AI (semgrep): execSync used only to check for ripgrep binary presence; not arbitrary execution. | ai | |
| source-diff | obfuscated-file:bundle/node_modules/@google/gemini-cli-devtools/dist/src/_client-assets.js | AI (source-diff): esbuild-minified React bundle with Google LLC license header; not obfuscated malware. | ai | |
| source-diff | obfuscated-file:bundle/node_modules/@google/gemini-cli-devtools/dist/client/main.js | AI (source-diff): esbuild-minified React bundle; recognizable React internals, no malicious indicators. | ai | |
| source-diff | obfuscated-file:bundle/node_modules/@google/gemini-cli-devtools/dist/src/_client-assets.d.ts | AI (source-diff): Type declaration file embedding the same minified client JS string; benign build artifact. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): env-spread passes process.env to child_process for binary execution; no exfiltration path evident. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used to run the downloaded binary; consistent with documented installer behavior. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall fetches versioned prebuilt binaries with SHA256 integrity checks; standard CLI installer pattern. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.2.17 | 0 / 0 | |
| 0.2.15 | 0 / 0 | |
| 0.2.6 | 2 / 0 | |
| 0.2.5 | 2 / 0 | |
| 0.2.4 | 2 / 0 | |
| 0.1.22 | 2 / 0 | |
| 0.1.5 | 2 / 0 | |
| 0.1.4 | 2 / 0 | |
| 0.1.3 | 2 / 0 | |
| 0.1.2 | 2 / 0 | |
| 0.1.1 | 2 / 0 | |
| 0.0.16 | 0 / 0 |
v0.2.17
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: qoder-dev.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.