OSINT Tooling Layer
1,100+ tools integratedA reconnaissance tooling layer that turns a sprawling open-source-intelligence catalog into a queryable, scriptable system: a filtering CLI over a tracked registry of more than 1,100 tools, plus credentialed API wrappers for the providers worth automating, with credential handling that never leaks a key.
The Problem
A thousand tools is not a capability. It is a pile.
The open-source intelligence space is enormous and unindexed: hundreds of tools per category, wildly different access models, paid versus free, passive versus active. A raw catalog is useless until you can filter it by what you actually need right now.
The Build
Make the catalog queryable and the APIs scriptable.
I built a tracked registry of the full catalog and a filtering CLI that slices it by category, keyword, opsec posture, pricing, and access requirements. For the providers worth automating, I wrote thin credentialed wrappers with a single safe path for missing keys.
What I built.
Tracked registry
More than 1,100 tools across 33 categories, sha256-tracked with a baseline so changes to the upstream catalog are visible and diffable.
Filtering CLI
A ten-flag query tool: filter by category, keyword, opsec posture, pricing, and whether a tool needs an API key, install, or registration.
Credentialed wrappers
Thin clients for eight providers including Shodan, VirusTotal, Censys, and GreyNoise, with a missing-key path that fails cleanly and never prints a secret.
Tech stack.
Core
- Python
- Standard library only
- JSON registry
- sha256 change tracking
Integrations
- Shodan
- VirusTotal
- Censys
- GreyNoise
- AbuseIPDB
- HIBP
- IPInfo
- SecurityTrails
Design
- Safe missing-key handling
- No secret leakage
- Idempotent sync
- Passive-by-default posture
What it demonstrates.
- •Integration breadth: many providers, one consistent, scriptable interface.
- •Security-domain fluency and disciplined credential handling.
- •Turning an unstructured catalog into a tool a person can actually drive.