Show HN: CIA World Factbook Archive (1990–2025), searchable and exportable (cia-factbook-archive.fly.dev)
A structured archive of CIA World Factbook data spanning 1990–2025.
It currently includes:
36 editions
281 entities
~1.06M parsed fields
full-text + boolean search
country/year comparisons
map/trend/ranking analysis views
CSV/XLSX/PDF export
The goal is to preserve long-horizon public-domain government data and make cross-year analysis practical.
Live: https://cia-factbook-archive.fly.dev
About/method details: https://cia-factbook-archive.fly.dev/about
Data source is the CIA World Factbook (public domain).
Not affiliated with the CIA or U.S. Government.
37 comments
[ 3.3 ms ] story [ 63.1 ms ] threadI didnt discover this until I saw the recent post about its deactivation.
One thing; you're supposed to write "Cannot confirm or deny my affiliation with the CIA"
[1] https://cia-factbook-archive.fly.dev/archive/2002
[2] https://cia-factbook-archive.fly.dev/archive/2002/GM
"A cache for datasets for the country profiles from the World Factbook in the original (1:1) format from the cia.gov website"
https://github.com/factbook/cache.factbook.json
It wasn't! Note to self: also check archive.org in case there is an internet archive for any sites an agent might reference.
I checked out this repo -- it has the information useful to my project. Thanks for sharing this!
One small bug though: https://cia-factbook-archive.fly.dev/analysis/compare?a=IN&b...
.. The second dropdown switches to "Comoros" instead of "China" even after selection, though URL says CN for China.
In case you are patching fields/bugs in database (like country codes for example), would it be possible for you to share that database as well with us so we can build on top?
This is actually an excellent dataset to test GraphRAG capabilities.
Also, a world simulation game, embodied with real data and real changes, can be built based off this data.
Thanks..
The pages are dense blocks of tiny gray serif text with default line height and almost no visual hierarchy. It feels like gray text on gray blobs. It is exhausting to scan and read.
In 2026, this should not be an issue. We have clear standards. The Web Content Accessibility Guidelines (WCAG) exist for a reason. Basic accessibility best practices have been documented for years.
https://wave.webaim.org/report#/https://cia-factbook-archive...
The issues are not subtle. Small text, low contrast, and long unbroken paragraphs are not design preferences. They are barriers. They make the content harder to read for everyone, especially people with visual or cognitive challenges.
This is fixable. Increase the base font size. Improve contrast ratios. Add meaningful spacing. Use clear headings and structure. These are foundational usability principles.
Accessibility is not extra polish. It is baseline quality. Right now, the site is unnecessarily hard to read. That is a design problem, not a content problem.