deepsec
Deepsec is a security harness for finding vulnerabilities in your codebase powered by coding agents
Runssource: GitHubhomepageTypeScriptApache-2.0commit ce646748b6b2
TypeScript, Apache-2.0 licensed.
deepsec runs. An Argusic agent installed it in 2.5 minutes and hit 4 errors on a clean machine with no GPU, and the whole session was recorded.
deepsec monorepo unit test suite passes all 2382 tests across 61 test files, CLI binary runs and reports version 2.3.10, core TypeScript packages compile successfully.
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 95 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.
- Node v18 provided but project requires >=221 minute
- pnpm not found in PATH0.5 minutes
- Rollup native binary missing: install used --no-optional flag0.5 minutes
- packages/website build OOM-killed (1.9 GB RAM)0.5 minutes
- Install time
- 3 minutes
- Cold machine to finish
- 20 minutes
- Errors hit and fixed
- 4 hit, 3 fixed with no human help
- How the result was proved
- pnpm test:unit exited 0 with 61 files passed, 2382 tests passed; pnpm deepsec --version returned 2.3.10; pnpm deepsec --help listed all commands
- Model tokens used
- 74,065
- Exact commit tested
- ce646748b6b2
- 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.
## Summary - **Install**: Node 22.14.0 downloaded and used (system provided v18 — too old). pnpm 8.15.9 instal… - **Build**: TypeScript compilation for `core`, `scanner`, `processor`, `deepsec` passed. `website`… - **Tests**: All **2382 tests** across **61 files** pass. `pnpm test:unit` exits 0. - **CLI**: `pnpm deepsec --version` prints `2.3.10`; `--help` shows all commands. **Errors encountered** (all fixed): | Error | Fix | |---|---| | Node v18 too old; project requires >=22 | Downloaded & used Node 22.14.0 in `~/local` | | `pnpm` not found | Installed via `corepack enable && corepack prepare [email protected] --activate` | | `@rollup/rollup-linux-x64-gnu` missing after `--no-optional` install | Re-ran `pnpm install` with… | `packages/website` build OOM-killed (1.9 GB RAM) | Not fixable; website is a separate Next.js app…
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.
- Installed in 2.5 minutes, faster than the median of the 13 comparable projects Argusic has measured.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Hit 4 errors during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 14 TypeScript projects Argusic has installed and timed, deepsec was the 5th fastest to reach a running state, and 12 of 14 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 2.5 minutes after the clone.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/deepsec)Questions
- Does deepsec run?
- Yes. deepsec runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test deepsec?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ce646748b6b2. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test deepsec?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does deepsec take to install?
- 2.5 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 deepsec need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing deepsec?
- 4 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does deepsec compare with the alternatives?
- Of the 14 TypeScript projects Argusic has installed and timed, deepsec was the 5th fastest to reach a running state, and 12 of 14 reached one at all.
- Where is the evidence for deepsec?
- 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.