Skip to content

Community

A directory built in the open

CyberAtlas is documentation as data: typed entries, reviewed before they are trusted, and open to correction. This page explains the process and where to start.

How a change becomes content

Nothing community-submitted is automatically verified. The status on every entry tells you where it sits in this pipeline.

  1. 01

    Contributor

    Someone who uses the tool hits a gap: a missing flag, an outdated install step, a broken assumption.

  2. 02

    Submission

    A change to a typed data file, or a request through the draft builders on this site. Provenance and sources included.

  3. 03

    Review

    A maintainer checks the claim against upstream documentation, the command syntax, and whether the framing stays responsible.

  4. 04

    Verification

    Only then does an entry move to Verified. Unreviewed material is labelled, never silently trusted.

  5. 05

    Publication

    The dataset revision bumps; search, category counts and activity feeds all derive from the same content.

Ways to help

Verification states

Always icon + label, never colour alone.

  • VerifiedReviewed by a CyberAtlas maintainer against the tool's own documentation.
  • CommunityContributor-submitted. Not every claim has been re-checked.
  • Needs reviewMay lag the current upstream release. Verify before relying on it.
  • OutdatedKnown to differ from the current version of the tool.
  • DeprecatedKept for reference. Do not treat this as the recommended path.

Content revisions

Dates describe when the dataset entry changed — 27 tool entries currently tracked. Upstream release dates are not implied.

The same feed drives the homepage, so nothing is maintained twice.