Project
About CyberAtlas Tool Directory
A reference for security tooling that behaves like documentation and is built like software: typed content, reusable components, no backend, no accounts.
The product answers a short list of questions for any tool: what it does, whether it runs on your platform, how to install it, which commands matter, what those commands actually do, where it goes wrong, what the alternatives are, and where it belongs in a learning path.
Everything is connected on purpose. A tool page links to its alternatives, the comparisons that cover them, the cheatsheet that condenses them, and the roadmap stages that assume them — so browsing turns into study without a search box in between.
Four rules that shape the product
They also explain what is missing: no star counts, no leaderboard, no live target, no neon.
Curate, do not scrape
Summaries are written from upstream documentation and linked back to it. A page that only mirrors a manual adds nothing.
Context over cleverness
A command with no explanation is a hazard. Every entry states what it does, what it needs, and how to read the output.
Honest metadata
Versions, dates and counts appear only when they are real. Optional fields are optional, so absence is a statement rather than a gap filled with fiction.
Documentation, not execution
Nothing on this site runs a command. There is no shell, no playground, no server-side execution — deliberately.
How the content is organised
Seven categories, each with subtopics; tools carry installation methods per platform and structured command entries; roadmaps, comparisons, cheatsheets and concepts reference tools by slug so links can never rot silently.
27 tools · 146 commands · 17 subtopics · 6 roadmaps · 10 concepts
Read the contribution guideTrust and safety
Verification states are explicit and always labelled. Legal framing, responsible use and the source policy are separate pages because a security reference should be legible about its own boundaries.