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 31 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

npm install succeeds with 504 packages, next build completes, all 845 tests pass, and the production standalone server serves all 10 tested API routes (health, stats, earthquakes, news, space-weather, fires, conflicts, maritime, flights, weather) with real data returning HTTP 200.

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.57 (measured)
recorded runs
2
last tested
stars
11,771
forks
2,451
open issues
30
watchers
172
size
13 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 osiris, 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.

  • next start with output:standalone kills itself ~30s after startup via setup-exception-listeners.js unhandledRejection handler calling process.exit(1).18 minutes
  • Standalone server.js defaults HOSTNAME to require('os').hostname() not 0.0.0.0, breaking external curl.5 minutes
  • Node.js 18.19.1 in container is below Next.js 16 minimum of Node 20.9.0; all bootstrap commands use the wrong runtime.3 minutes
Install time
31 minutes
Cold machine to finish
76 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
npm test exited 0, 71 files / 845 tests passed; curl 10 API endpoints on production standalone server returned HTTP 200 for all; server stayed alive and responsive for 100+ seconds
Model tokens used
2,267,317
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.

/api/flights?bounds=-10,40,35,65 => 200
/api/weather => 200
==== stats payload:
{'flights': 6129, 'sats': 5028, 'cctv': 33235, 'weather': 17, 'nuclear': 64, 'incidents': 231}
==== news count:
news items: 107
==== space-weather:
KP: 1 Flares: 1
Everything works great — 10/10 endpoints return HTTP 200 with real data. No mocks needed — all data…
tokens used
2,267,317
Everything works great — 10/10 endpoints return HTTP 200 with real data. No mocks needed — all data…

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 3 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.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 31 minutes to install, slower than the median of the 35 comparable projects Argusic has measured.

Of the 36 TypeScript projects Argusic has installed and timed, osiris was the 36th fastest to reach a running state, and 30 of 36 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.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.57
Argusic Runner1/3Runs100.000.04

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/osiris.svg)](https://argusic.com/subject/osiris)

Questions

Does osiris run?
Yes. osiris runs. Argusic installed and launched it on a clean machine in 31 minutes, hitting 3 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. 2 attempts are 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.57: 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?
31 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?
3 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 osiris compare with the alternatives?
Of the 36 TypeScript projects Argusic has installed and timed, osiris was the 36th fastest to reach a running state, and 30 of 36 reached one at all.
Where is the evidence for osiris?
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.

Discussion