IRONSIGHT
A browser dashboard that watches two wars. IRONSIGHT (Nobler Works, MIT, ~564★ / 123 forks, TypeScript on Next.js 16) pulls about a dozen free public feeds onto one screen and lets the viewer flip the whole screen between the Iran/Israel and Russia/Ukraine theatres. Every panel re-points at the selected region: news, sirens, aircraft, markets, satellite heat.
It is the spoke’s first conflict-monitoring tool, and its first tool that answers “what is happening there” instead of “who is this person” (llm-osint, gitsint) or “what is exposed on this platform” (swaggerspy).
What it aggregates
| Feed | What it supplies |
|---|---|
| Google News RSS | ~15 outlets per theatre, noise-filtered |
| Telegram public channels | scraped through the embed view, auto-translated (Hebrew, Arabic, Farsi, Ukrainian, Russian) |
| adsb.lol | military aircraft positions, community ADS-B network |
| Tzeva Adom (Pikud HaOref mirror) | Israeli Home Front Command sirens |
| alerts.com.ua | Ukrainian oblast air-raid state |
| neptun.in.ua | drone and missile tracks |
| NASA FIRMS | thermal anomalies — fires and explosions — clipped to the theatre |
| Yahoo Finance · CoinGecko · Polymarket | defence stocks, oil and gas, crypto, prediction-market odds |
Positions and strike markers land on a Leaflet map over a CARTO basemap with Natural Earth borders. Polling is tiered by how fast the thing moves: sirens every 15 seconds, drone tracks every 20, Telegram every 60, news every 90, strikes every 2 minutes, naval every 5, markets and satellite every 10.
Three things the repository establishes
No API keys, anywhere. Every row in the table above is free and unauthenticated. npm install,
npm run dev, or docker compose up behind a ~215 MB image running as non-root. This is the same
cost-floor story termux tells from the hardware side, now at the feed layer: a synoptic view of
two active conflicts costs nothing and needs no account with anyone.
No AI, and no conclusion. IRONSIGHT does not summarize, score, or infer. It routes, filters, and draws. On the autonomy axis this spoke has been tracking, it sits behind the manual toolkit — closer to kafsiem‘s analyst-in-the-loop pole than to llm-osint‘s, except that where kafsiem builds an auditable entity graph, IRONSIGHT builds a wall of panels and leaves the correlation entirely to the eye. The only translation step (Google Translate’s unofficial endpoint) is machine, unreviewed, and applied to feeds nobody in the intended audience can necessarily read.
The feed list mixes adversaries without marking them. The Eastern Europe roster carries TASS, RT and the Moscow Times alongside Reuters, the Kyiv Independent and Meduza; the Middle East roster carries PressTV alongside Haaretz and the Jerusalem Post. The README lists them in one undifferentiated block. Whether that is a bug or the point is a real question — an analyst wants to see what each side is saying — but the interface has no reliability marking, and the same is true of the scraped Telegram channels. This is osint-overview-wikipedia‘s source-contamination risk arriving as a design choice rather than as an accident, and it is the sharpest thing this source contributes.
What the project says about itself
The README is unusually frank about its own footing. It calls IRONSIGHT “a viewer that surfaces publicly available, third-party, open-source feeds” and claims “no ownership or credit for any third-party data.” It then states that several endpoints — Yahoo Finance, Google Translate, Telegram embeds, community feeds — are undocumented, “may violate provider terms of service,” and “could stop working without notice.” Liability for legal and ToS compliance is pushed to the user; the software is “as-is,” “intended for educational demonstration, not commercial use.”
So the sourcing is honest and the legal ground is admitted to be soft. Compare awesome-osint-list, which carries no disclaimer at all: IRONSIGHT names every provider and every risk. That is why it grades T3 rather than T4 despite being a project describing itself — the self-description includes the weaknesses.
The last line of the README is a sales pitch: Nobler Works is “available for engagement” for custom tools like this one. The repository is a demonstration piece.
Limits of this record
Nothing here is verified against a run. Star counts, feed lists and polling intervals are a 2026-08-10 snapshot of the README, and the undocumented endpoints mean the feed table has a short half-life by the project’s own admission. No accuracy claim is made anywhere in the source, by the project or by anyone else — an ADS-B network showing “military aircraft” is showing aircraft that chose to transmit, and a thermal anomaly is a hot pixel, not a strike.