HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
davidteter
OPEN-RISOP
Data & Databases2022–2024
davidteter / OPEN-RISOP

OPEN-RISOP

This is an attempt to build an open-sourced version of the Red Integrated Strategic Operational Plan (RISOP) using an open-sourced targeting database and weapon allocation modules and consequence of execution tools.

4Distinct people
7Mentions
0Explicit recommenders
148GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

This is an attempt to build an open-sourced version of the Red Integrated Strategic Operational Plan (RISOP) using an open-sourced targeting database and weapon allocation modules and consequence of execution tools.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month7 dated mentions

Observed mentions: 2022-03-24 19:07:24 UTC to 2024-01-20 21:24:44 UTC.

0123452022-03-01 00:00:00 UTC to 2022-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 20222022-04-01 00:00:00 UTC to 2022-05-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2022-05-01 00:00:00 UTC to 2022-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-01 00:00:00 UTC to 2022-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-07-01 00:00:00 UTC to 2022-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-01 00:00:00 UTC to 2022-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-01 00:00:00 UTC to 2022-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-01 00:00:00 UTC to 2022-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-01 00:00:00 UTC to 2022-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-12-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2023-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-01 00:00:00 UTC to 2023-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 20232023-03-01 00:00:00 UTC to 2023-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-01 00:00:00 UTC to 2023-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-01 00:00:00 UTC to 2023-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-01 00:00:00 UTC to 2023-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-07-01 00:00:00 UTC to 2023-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-08-01 00:00:00 UTC to 2023-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-01 00:00:00 UTC to 2023-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-01 00:00:00 UTC to 2023-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-01 00:00:00 UTC to 2023-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-12-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2024-02-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 20222022-03-01 00:00:00 UTC2022-04-01 00:00:00 UTC101
Apr 20222022-04-01 00:00:00 UTC2022-05-01 00:00:00 UTC514
May 20222022-05-01 00:00:00 UTC2022-06-01 00:00:00 UTC000
Jun 20222022-06-01 00:00:00 UTC2022-07-01 00:00:00 UTC000
Jul 20222022-07-01 00:00:00 UTC2022-08-01 00:00:00 UTC000
Aug 20222022-08-01 00:00:00 UTC2022-09-01 00:00:00 UTC000
Sep 20222022-09-01 00:00:00 UTC2022-10-01 00:00:00 UTC000
Oct 20222022-10-01 00:00:00 UTC2022-11-01 00:00:00 UTC000
Nov 20222022-11-01 00:00:00 UTC2022-12-01 00:00:00 UTC000
Dec 20222022-12-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
Jan 20232023-01-01 00:00:00 UTC2023-02-01 00:00:00 UTC000
Feb 20232023-02-01 00:00:00 UTC2023-03-01 00:00:00 UTC000
Mar 20232023-03-01 00:00:00 UTC2023-04-01 00:00:00 UTC000
Apr 20232023-04-01 00:00:00 UTC2023-05-01 00:00:00 UTC000
May 20232023-05-01 00:00:00 UTC2023-06-01 00:00:00 UTC000
Jun 20232023-06-01 00:00:00 UTC2023-07-01 00:00:00 UTC000
Jul 20232023-07-01 00:00:00 UTC2023-08-01 00:00:00 UTC000
Aug 20232023-08-01 00:00:00 UTC2023-09-01 00:00:00 UTC000
Sep 20232023-09-01 00:00:00 UTC2023-10-01 00:00:00 UTC000
Oct 20232023-10-01 00:00:00 UTC2023-11-01 00:00:00 UTC000
Nov 20232023-11-01 00:00:00 UTC2023-12-01 00:00:00 UTC000
Dec 20232023-12-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
Jan 20242024-01-01 00:00:00 UTC2024-02-01 00:00:00 UTC101

What Hacker News says

7 sources
To my knowledge, no Russian targeting plans have ever been declassified, but an open source project called OPEN-RISOP[^1] has a few hypothetical attack plans that give some idea of what would be targeted. Its creator, David Teter, is a former advisor to USSTRATCOM, DIA, and DTRA on strategic plans (SIOP/OPLANs 8044/8010), kinetic and non-kinetic weapon effects, vulnerability analysis, and targeting. It's raw data, so to get a visualization you need to use something like Nuclear War Simulator[^2]†. Here's a video showing one such plan: https://www.youtube.com/watch?v=WF0mEOCK2KE [^1]: https://github.com/davidteter/OPEN-RISOP [^2]: https://nuclearwarsimulator.com † NWS is on Steam, but don't go into it expecting a game-like experience. It's more of a rather technical "what-if" simulator.
In 1,100 Declassified U.S. Nuclear Targets
Elsewhere in this thread he links to David Teter's OPEN-RISOP as his source. [1] The quality of OPEN-RISOP is generally pretty good, and the author worked at Sandia National Labs about 10-20 years ago. Targeting at least is pretty consistent with what I'd expect as high value targets. OPEN-RISOP's counterforce + countervalue scenario only tallies about 60M fatalities (~20% of US population) from the original attack. chakalakaps must be assuming cascading failures of infrastructure & food production after the initial attack (a la Threads [2]). While this is a distinct possibility, it's far from a given - and this is also one of those areas where being prepared (eg. having a year of dried foodstuffs stored, or a small personal garden) can give you a distinct survival advantage. [1] https://github.com/davidteter/OPEN-RISOP/tree/main/TARG
Read the rest
In How destructive are nuclear weapons really?
There are multiple plans for multiple contingencies. A couple of different examples are here: https://github.com/davidteter/OPEN-RISOP The fallout thing is kinda a unlikely thing. Fallout from typical ground-bursts is something that denies area for weeks at most. There are weapons systems that can do area denial for much longer by using weapons salted with materials that will remain radioactive for many years (essentially the plot of Dr. Strangelove -- that "doomsday" system is based on realistic weapons possibilities, and the Russians in the past decade intimated that they have developed a submersible drone system designed to cross the ocean and detonate huge salted weapons to poison the U.S. coasts for decades https://en.wikipedia.org/wiki/Status-6_Oceanic_Multipurpose_... ) -- but as far as anyone in the open source info world knows,
Read the rest
these kinds of weapons are not deployed.
In How destructive are nuclear weapons really?
Main GitHub page: https://github.com/davidteter/OPEN-RISOP A former U.S. nuclear warplanner (https://www.linkedin.com/in/dmteter) is developing an open source target database and target laydowns against U.S. targets, assuming a Russian attack in present day. He focuses on three scenarios, two excursion scenarios (a pure "counterforce" attack in which Russia only targets U.S. nuclear weapons, a pure "countervaule" attack in which Russia focuses entirely on creating maximum death and damage to infrastructure) and one main scenario that would generally be considered the most likely type of attack, which is a blend of counterforce and countervalue. Some notes I've taken from his reddit and Twitter explanations: this attack is modeled against the U.S. only. He did not attempt to do targeting for the EU theatre as that gets into his previous
Read the rest
job, which was very intimately familiar with a lot of classified stuff that he doesn't want to build into a map; however, he said that EU/APAC/maybe China theatre would be targeted, mostly with shorter range "tactical" weapons. He did a ton of work, calculating VNTK (https://acronyms.thefreedictionary.com/VNTK) for each target, and planned his attack just like he used to plan attacks against the Russian theatre, making sure to hit things like spent fuel storage for area denial, hitting the right dams to cascade fail hydrology management on major rivers (Baton Rouge would be under a couple hundred feet of water within a few weeks and would be "scoured clean"), etc. In the end, he estimates that 95 percent of the U.S. population would be dead within 18 months of the attack due to complete lack of infrastructure, food, water, medicine, medical treatment, logistics, heat, power, etc.
In Open-RISOP: A former U.S. Nuclear warplanner's attack plans against the U.S.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.