sightline

An OSINT search engine for mapping real-world infrastructure from OpenStreetMap data

Runssource: GitHubhomepageTypeScriptMITcommit 1095b9275f83

TypeScript, MIT licensed. The project labels itself: geo osint, geoint, openstreetmap, openstreetmap api, openstreetmap data, osint and overpass turbo.

sightline runs. An Argusic agent installed it in 18 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 and next build succeed; dev server starts on port 3000, homepage serves 200, and the search API returns real OpenStreetMap infrastructure data via Nominatim geocoding and Overpass API queries.

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 60 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
60 / 100
cost of the verifying run
$0.04 (measured)
recorded runs
2
last tested
stars
577
forks
76
open issues
0
watchers
6
size
8 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 sightline, 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.

  • Node.js v18.19.1 too old for Next.js 16 (requires >=20.9.0)2 minutes
  • next.config.ts had unrecognized key reactCompiler (Next.js 16 feature)1 minute
  • eslint.config.mjs imported submodules not found in eslint-config-next v151 minute
Install time
18 minutes
Cold machine to finish
12 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
curl -X POST http://localhost:3000/api/search -H 'Content-Type: application/json' -d '{"query":"type:telecom region:karnataka"}' returned 200 with 148 results from real OSM/Overpass API
Model tokens used
267,093
Exact commit tested
1095b9275f83
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.

*Fix:* Changed to import from `eslint-config-next` directly.
**Build** — `npm run build` succeeds, compiles all pages and API routes.
**Launch & verify** — Dev server starts on port 3000, homepage returns 200 with full HTML. POST to …
exec
/bin/sh -lc "ARGUSIC_RESULT:{\"install_succeeded\":true,\"launch_succeeded\":true,\"install_minutes…
 exited 127 in 0ms:
/bin/sh: 1: ARGUSIC_RESULT:{install_succeeded:true,launch_succeeded:true,install_minutes:18,errors:…
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT:{\"install_succeeded\":true,\"launch_succeeded\":true,\"install_m…
 succeeded in 0ms:
tokens used
267,093

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 18 minutes.
  • 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 it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

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 Runner2/3Runs100.000.04
Argusic Runner1/3Did not run20.000.01

Topics (from GitHub)

geo-osintgeointopenstreetmapopenstreetmap-apiopenstreetmap-dataosintoverpass-turbo

Embed the badge

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

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

Questions

Does sightline run?
Yes. sightline runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test sightline?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1095b9275f83. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test sightline?
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 sightline take to install?
18 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 sightline need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing sightline?
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.
Where is the evidence for sightline?
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