dsh-hub-cli

Open-source CLI, schemas, resolver, and DSH agent tools for DSH Plugin Hub

Runssource: GitHubhomepageTypeScriptMITcommit 1805424c762d

TypeScript, MIT licensed. The project labels itself: ai agent, cli, deepseek harness, developer tools, dsh plugin, plugin manager and typescript.

dsh-hub-cli runs. An Argusic agent installed it in 8 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

DSH Hub CLI workspace installs, builds, and passes the full test suite (326/326) along with typecheck and package-content/governance checks when run under Node 22.23.4 and pnpm 10.33.0, and the dsh-hub binary answers --version with 0.5.0.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.01 (measured)
recorded runs
1
last tested
stars
274
forks
0
open issues
5
watchers
1
size
1 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing dsh-hub-cli, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Container only has Node v18.19.1 and no pnpm/corepack; project requires Node >=22.13 and pnpm 10.334 minutes
Install time
8 minutes
Cold machine to finish
2 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
pnpm test exited 0 (326 tests, 326 pass, 0 fail); node packages/cli/dist/bin.js --version printed 0.5.0; --help printed full usage; pnpm typecheck, pack:check, governance:check all exit 0
Model tokens used
89,612
Exact commit tested
1805424c762d
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

**Result: repository works as a brand-new user.** The only gap was the environment: the container s…
**Verified with these commands and their actual output:**
- `pnpm install --frozen-lockfile` → "Done in 629ms", added 24 packages (only a benign warning abou…
- `pnpm build` → schemas, registry, cli all built via `tsc` with exit 0.
- `pnpm test` → build + test runner, `# tests 326`, `# pass 326`, `# fail 0`, `# skipped 0`.
- `pnpm typecheck` → all three packages exit 0.
- `pnpm pack:check` → all 4 packages audited.
- `pnpm governance:check` → "repository governance check passed (27 required files)".
- `node packages/cli/dist/bin.js --version` → `0.5.0`.
- `node packages/cli/dist/bin.js --help` → printed full usage (exit 0).
- `node packages/cli/dist/bin.js telemetry state --json` → `{"enabled":false,...}`.
No mock server was necessary — the test suite mocks the Hub internally; no real third-party credent…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Took 8 minutes to install, slower than the median of the 83 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 84 ai-agent projects Argusic has installed and timed, dsh-hub-cli was the 55th fastest to reach a running state, and 58 of 84 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 8 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.01

Topics (from GitHub)

ai-agentclideepseek-harnessdeveloper-toolsdsh-pluginplugin-managertypescript

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/dsh-hub-cli.svg)](https://argusic.com/subject/dsh-hub-cli)

Questions

Does dsh-hub-cli run?
Yes. dsh-hub-cli runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test dsh-hub-cli?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1805424c762d. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test dsh-hub-cli?
The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does dsh-hub-cli take to install?
8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does dsh-hub-cli need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing dsh-hub-cli?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does dsh-hub-cli compare with the alternatives?
Of the 84 ai-agent projects Argusic has installed and timed, dsh-hub-cli was the 55th fastest to reach a running state, and 58 of 84 reached one at all.
Where is the evidence for dsh-hub-cli?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion