The original repository has been deleted or made private. This page is an archival snapshot from indexing time; the install command may no longer work.
Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
Data as of (UTC)
What it doesAI
CLI and MCP server for fine-tuning LLMs on code repositories via Tuning Engines governed AI runtime.
- CLI and MCP server for Tuning Engines
- Fine-tune LLMs on code repositories
- Govern AI workflows via one OpenAI-compatible API
Capability tags are AI-inferred or rule-extracted from the README (see badge) — vocabulary-limited, not install-verified. AI = inferred; README = literal keyword from the readme.
Installation
dsh plugin --profile web add tuningengines-cliInstall method: GitHub · sandbox install ok, web smoke failed (L5) · verified on dsh 0.2.1-rc.2
Trends
Four lines, four questions: total stars, stars gained this week, cumulative downloads, downloads this week. The GitHub pair comes from real-read sampling — a rotating daily shard, so one plugin is re-read roughly every 5–14 days, sparser than npm; the npm pair has a value on every snapshot day. The two cumulative panels are smoothed curves with no sample markers; the two weekly panels keep their raw bars and add a 4-week moving-average trend line that strips single-week noise down to the direction of travel.
3 samples (roughly every 11 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 10-14 · 3 points
Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend
Only 2 points (< 3): no chart yet
10-02 → 10-14 · 2 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
Bars = the snapshot’s last-week rolling window (official npm + npmmirror combined); line = 4-week moving-average trend — the shape of weekly demand, not a user count
09-17 → 10-18 · 28 points
Verification & Compatibility
Grouped by plugin version: each card lists the dsh versions actually tested against that artifact version and their install verdicts (L5 wins). Untested combinations are omitted — absence means untested, never assumed compatible. L1–L3 are a plugin-level static archive (independent of the dsh version — the same verdict on every dsh row): they sit in each row's level grid next to L4/L5, marked "static", while their evidence is stored once per plugin inside that row's "checks & evidence" instead of being duplicated per version.
External credentials (plugin-level): none detected
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin ＼ dsh | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 | dsh 0.2.0-rc.1 |
|---|---|---|---|---|---|
| 0.4.35 | ✗ | ✗ | ✗ | ✗ | ✗ |
| 0.3.5 | · | · | · | · | · |
| v0.3.5 | · | · | · | · | · |
0.4.35npm10 failed2026-10-19
tuningengines-cli
✗dsh 0.2.1-rc.22026-10-19L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · tuningengines-cli@0.4.35
ID: tuning-engines-cli@0.4.35@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-alpha.42026-10-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · tuningengines-cli@0.4.35
ID: tuning-engines-cli@0.4.35@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-alpha.22026-10-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · tuningengines-cli@0.4.35
ID: tuning-engines-cli@0.4.35@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.0-rc.22026-10-09L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · tuningengines-cli@0.4.35
ID: tuning-engines-cli@0.4.35@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.0-rc.12026-09-29L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · tuningengines-cli@0.4.35
ID: tuning-engines-cli@0.4.35@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.7-rc.22026-09-25L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · tuningengines-cli@0.4.35
ID: tuning-engines-cli@0.4.35@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.7-rc.12026-09-24L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · tuningengines-cli@0.4.35
ID: tuning-engines-cli@0.4.35@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.6-alpha.22026-09-20L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · tuningengines-cli@0.4.35
ID: tuning-engines-cli@0.4.35@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.6-alpha.12026-09-17L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · tuningengines-cli@0.4.35
ID: tuning-engines-cli@0.4.35@dsh0.1.6-alpha.1 · profile: l3-fullscan
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-04L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · tuningengines-cli@0.4.35
ID: tuning-engines-cli@0.4.35@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.3.5npm2026-09-16
tuningengines-cli
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v0.3.5github2026-09-13
https://github.com/cerebrixos-org/tuning-engines-cli
○dsh 0.1.5-rc.22026-09-13not tested
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/cerebrixos-org/tuning-engines-cli#v0.3.5
ID: tuning-engines-cli@v0.3.5@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.3-alpha.22026-09-09not tested
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/cerebrixos-org/tuning-engines-cli#v0.3.5
ID: tuning-engines-cli@v0.3.5@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.3-alpha.12026-09-07not tested
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/cerebrixos-org/tuning-engines-cli#v0.3.5
ID: tuning-engines-cli@v0.3.5@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.2-rc.12026-09-05not tested
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/cerebrixos-org/tuning-engines-cli#v0.3.5
ID: tuning-engines-cli@v0.3.5@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
Only the latest 3 published versions are shown; source-snapshot (commit hash) groups, unstated groups and older versions are omitted — the full archive stays in the data layer (snapshot/unstated groups appear only when a plugin has no published version).
Author badges
Embed the dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/tuning-engines-cli/?ref=badge)`dsh.so is an independent community project, not affiliated with or endorsed by DeepSeek AI. Badges are maintained by dsh.so; embed links carry a ?ref= attribution parameter.
Security Report
Two automated layers, neither a manual review: a static scan (per-plugin rule checks) and a model-driven dynamic security audit that covers only the subset static-flagged at warn or above and never executes plugin code.
Static low; dynamic high (authoritative when present) → overall high.
v0.3.5v0.3.5git2026-10-18v0.3.5same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (4)
- criticalshellExec · shell
src/commands/auth.ts:18exec(cmd, (err) => { - criticalshellExec · shell
src/commands/billing.ts:19exec(cmd, (err) => { - warningfsWrite · files
src/config.ts:67fs.writeFileSync(CONFIG_FILE, JSON.stringify(config, null, 2) + "\n", { - warningfsWrite · files
src/config.ts:92fs.writeFileSync(CONFIG_FILE, JSON.stringify(config, null, 2) + "\n", {
show 4 audit findings
- highServer-returned verification_url is interpolated into a shell command in openBrowser (auth login)
src/commands/auth.ts:18verification_url comes unvalidated from the response of POST /api/v1/auth/device. Double quotes do not neutralise command substitution in sh (`$(...)`, backticks), so a hostile or compromised API endpoint (or an api_url the user was persuaded to set with `te config set-url` / TE_API_URL, including a plain http host that a network attacker can answer) yields arbitrary command execution on the developer's machine during `te auth login`.
- mediumConfigurable api_url is concatenated into the same shell exec in billing add-credits
src/commands/billing.ts:19apiUrl is taken verbatim from config (TE_API_URL or `te config set-url`) with no scheme/host validation, so a value containing quote-breaking characters and shell metacharacters executes commands locally when the user runs `te billing add-credits`. Lower than the auth case because it needs local configuration control, but it is the same injection sink with no escaping.
- mediumAPI base URL is unvalidated and allows plaintext HTTP for the Bearer token and forwarded AWS/GitHub secrets
src/config.ts:56`te config set-url` and TE_API_URL accept any string, and the HTTP client downgrades to plain `http` when the URL is not https. A plaintext or look-alike host receives the `Authorization: Bearer <api key>` header, plus the S3 secret access keys and GitHub tokens that the commands forward, in clear text on the wire.
- lowLong-lived S3/GitHub credentials accepted as command-line arguments (shell history, process list, AI transcripts)
src/commands/jobs.tsSecrets passed as argv are visible in `ps` output and persisted in shell history; the MCP variants (src/mcp.ts import_model/export_model/validate_s3) additionally place them in model-visible tool arguments, so they end up in assistant conversation logs. No local filesystem exfiltration, but a broadened exposure surface for long-lived credentials.
Tuning Engines CLI/MCP client; the only real risk is server/config-supplied URLs interpolated into a shell exec for browser opening, plus plaintext-HTTP token use.
Rule (2026-10-28): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); the static scan tier (vet primary, dsh backstop) applies only when there is none (not queued / audit failed / withdrawn). The audit never writes the exemption list (exemptions are manual only); a wrong conclusion is withdrawn by human review and the tier falls back to the static scan tier.
Disclaimer: the static scan and the dynamic security audit are both automated analysis, not a security guarantee. Always review what you install.
Activity
Last commit 2026-08-18 · activity: Stable
• Repo created: 2026-03-15
• Stars: ★ 6 · Forks: 4
• Health: Stable — committed within 90 days
Source
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
Frequently asked questions
What is tuning-engines-cli?
tuning-engines-cli is a DeepSeek Harness (dsh) plugin listed on dsh.so — an independent community registry that indexes public source repositories and publishes automated security-scan and install-verification results for each entry.
Is dsh.so or this plugin page official?
dsh.so is an independent community registry and is not affiliated with, endorsed by, or sponsored by DeepSeek AI.
How do I install tuning-engines-cli?
Run dsh plugin --profile web add github:cerebrixos-org/tuning-engines-cli#v0.3.5 in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4); the web smoke test (L5) has not passed yet.
How does the security scan relate to a manual audit?
Both layers are automated, not a manual audit. The static scan is heuristic analysis of the repository source, so it can produce false positives and miss context. The model-driven dynamic security audit only covers plugins static-flagged at warn or above, never executes plugin code, and its conclusion is authoritative when there is one (it may raise or lower the static tier); exemptions stay manual. Neither layer is an endorsement: review the repository and the permissions it asks for before installing, together with the verification level and health signals.
How fresh is the data on this page?
The data on this page is as of 2026-11-08 (UTC) — the most recent valid timestamp among the registry refresh, install verification, security scan and dynamic audit. Build time is never used as a data date.