osiris
Open Source Global Intelligence Platform - Real-Time OSINT Dashboard - A Palantir Alternative - 2nZNHm3Lr9umG3DVrzYwHgktwkuKuJRXqqRqs3ewpump
Runssource: GitHubhomepageTypeScriptMITcommit 954dbc9c39cf
TypeScript, MIT licensed.
osiris runs. An Argusic agent installed it in 8 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install and npm run build succeed; all 845 unit tests pass (71 test files); the Next.js standalone server starts on port 3000 and the health endpoint responds HTTP 200 with a valid JSON payload.
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
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.
- Build failed because Node.js 18.19.1 is too old for Next.js 16.3.4 (requires >=20.9.0)5 minutes
- PostCSS native binding @tailwindcss/oxide not found — npm failed to install the optional native binary for linux-x64-gnu2 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npm test exited 0, 71 files 845 tests passed; curl http://127.0.0.1:3000/api/health returned 200 with JSON object containing status:'serving' and uptime_seconds:3
- Model tokens used
- 173,136
- Exact commit tested
- 954dbc9c39cf
- 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.
✓ Ready in 0ms
✓ Running next.config took 3ms
{"status":"serving","scope":"process","checks_performed":"none","detail":"The application process i…
200
The app is running and the health endpoint returns a proper JSON response. Let me kill the server a…
exec
/bin/sh -lc 'kill %1 2>/dev/null; pkill -f "server.js" 2>/dev/null; echo "done"' in /work/repo
exited 143 in 0ms:
Let me kill lingering processes and compile the report.
tokens used
173,136
Let me kill lingering processes and compile the report.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 8 minutes.
- Recovered from all 2 errors 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
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 11 TypeScript projects Argusic has installed and timed, osiris was the 6th fastest to reach a running state, and 9 of 11 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.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/osiris)Questions
- Does osiris run?
- Yes. osiris runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test osiris?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 954dbc9c39cf. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test osiris?
- 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 osiris 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 osiris need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing osiris?
- 2 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 osiris compare with the alternatives?
- Of the 11 TypeScript projects Argusic has installed and timed, osiris was the 6th fastest to reach a running state, and 9 of 11 reached one at all.
- Where is the evidence for osiris?
- 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.