harbor
Stop configuring your AI stack. Start using it. One command brings a complete pre-wired LLM stack with hundreds of services to explore.
Runs with mockssource: GitHubhomepagePythonApache-2.0commit 4c20a822f61e
Python, Apache-2.0 licensed. The project labels itself: ai, automation, bash, cli, container, docker, docker compose and homelab.
harbor runs, with stand-ins for the services it depends on. An Argusic agent installed it in 12 minutes and hit 4 errors on a clean machine with no GPU, and the whole session was recorded.
Harbor CLI v0.5.6 installed from source, frontend web app builds, all Deno-based unit tests (41 total) pass, lint self-test green (12 bash rules, 9 compose rules, 1 boost rule, 3 orchestrator checks). Docker-dependent container test matrix blocked.
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 66 of 100 (the mean of this project's run scores).
At a glance
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Deno not installed in container2 minutes
- Deno lockfile version mismatch (v5 from newer Deno, installed Deno 2.2.0 writes v4)1 minute
- Docker daemon not available (no root access)
- shellcheck not installed (optional, used by lint)
- Install time
- 12 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 4 hit, 2 fixed with no human help
- Model tokens used
- 119,600
- Exact commit tested
- 4c20a822f61e
- 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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
2. **Deno not installed**: No Deno in the container. **Fix**: Downloaded Deno binary from GitHub re… 3. **No Docker**: The Harbor project requires Docker to run services and the container-based test m… 4. **No shellcheck**: Lint self-test reported SKIP for shellcheck fixtures. **Fix**: Not needed - t… **What was verified to work (without Docker):** - **Lint self-test**: 12 bash rules PASS, 9 compose rules PASS, 1 boost rule PASS, 3 orchestrator c… - **Full lint passes**: `--bash-rules`, `--compose`, `--boost` all report "clean" - **Docs unit tests**: 13 tests across 3 test files, all PASS - **Test orchestrator unit tests**: 5 tests, all PASS (materializeTrackedRepo, no bind-mount guard,… - **macOS requirements tests**: 22 stubbed tests, all PASS - **Tauri app frontend**: TypeScript compiles cleanly (0 errors), Vite build succeeds producing pro… - **CLI commands work**: `harbor version`, `harbor config get/set`, `harbor skills`, `harbor help` - **Frontend npm install**: 305 packages installed cleanly
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
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 12 minutes to install, slower than the median of the 36 comparable projects Argusic has measured.
- Hit 4 errors during setup, 2 of which were not solved.
Of the 37 ai projects Argusic has installed and timed, harbor was the 30th fastest to reach a running state, and 30 of 37 reached one at all.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Did not run | 50.00 | 0.05 | |
| Argusic Runner | 2/3 | Runs with mocks | 82.00 | 0.08 |
Topics (from GitHub)
aiautomationbashclicontainerdockerdocker-composehomelabllmlocalmcpnpmpackagepypisafetensorsself-hostedservertooltools
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/harbor)Questions
- Does harbor run?
- harbor runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 12 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test harbor?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4c20a822f61e. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test harbor?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does harbor take to install?
- 12 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 harbor need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing harbor?
- 4 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does harbor compare with the alternatives?
- Of the 37 ai projects Argusic has installed and timed, harbor was the 30th fastest to reach a running state, and 30 of 37 reached one at all.
- Where is the evidence for harbor?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.