Tracking issue for cross-link PRs to authoritative curated lists. Each is a separate PR opened from a personal fork; this issue tracks them.
Why: agents and humans both query awesome-* lists when looking for tools in a category. A single accepted entry compounds discovery across crawlers, RAG indexes, and human readers.
Candidate lists
Acceptance per PR
Each submission needs:
- The repo's required entry format (markdown line, often
- [name](url) - description)
- Compliance with their CONTRIBUTING.md (alphabetical order, line length, etc.)
- A short justification in the PR body referencing concrete differentiators: schema-v1 contract, SLSA L3, cosign keyless, NIST 800-63B-4 entropy floors, EFF wordlist verification at startup.
Out of this issue
Newsletter mentions and conference proposals are tracked elsewhere (or not at all). This issue is just curated-list submissions.
Spawned from #13 after the per-registry work finished.
Tracking issue for cross-link PRs to authoritative curated lists. Each is a separate PR opened from a personal fork; this issue tracks them.
Why: agents and humans both query awesome-* lists when looking for tools in a category. A single accepted entry compounds discovery across crawlers, RAG indexes, and human readers.
Candidate lists
avelino/awesome-go— "Security" or "Command Line / Productivity" section. Strict gate (must have tests, godoc, active maintenance, ≥30 days old) — we satisfy all of these.agarrharr/awesome-cli-apps— broad CLI directory.sindresorhus/awesome-cryptography— strict, expects citations of cryptographic claims (we have NIST SP 800-63B-4 / 800-131A in docs/CRYPTO.md).sger/awesome-llm-cli— LLM-tooling specific.Lissy93/personal-security-checklist— security-focused.Acceptance per PR
Each submission needs:
- [name](url) - description)Out of this issue
Newsletter mentions and conference proposals are tracked elsewhere (or not at all). This issue is just curated-list submissions.
Spawned from #13 after the per-registry work finished.