reach-security
No liveness check has reached it yet; it is registered on GitHub and PyPI and has been in the index since 11 Oct 2026. How this is checked
Reach Security is an open-source CLI and analysis tool for reasoning about AWS IAM permissions. It uses SMT-based formal verification to produce proofs and witnesses showing what credentials and AI agents can access, including potential privilege-escalation paths.
Inferred · not functionally tested
Overview
6 featuresPurpose: Determining and proving which AWS resources cloud credentials and AI agents can reach, including privilege-escalation paths.
Inferred · not functionally tested
Audience: cloud security engineers and developers auditing AWS IAM permissions
Inferred · not functionally tested
Functions: analytics
Inferred · not functionally tested
Interfaces: API: unknown · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: open_source · license: AGPL-3.0 · platforms: CLI · deployment: cli, self_hosted
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: pypi.org · github.com. These links do not verify the individual claims.
In the AI & LLM security space, reach-security takes a focused approach. Inferred · not functionally tested: It focuses on determining and proving which AWS resources cloud credentials and AI agents can reach, including privilege-escalation paths. Inferred · not functionally tested: It is built as an open-source project for cloud security engineers and developers auditing AWS IAM permissions. Basis unknown · not verified: reach-security is open source under the AGPL-3.0 license. Basis unknown · not verified: It runs on the command line, and it can be self-hosted.
ctrl-adam builds and maintains reach-security, and it first shipped in 2026. Development happens publicly on GitHub with 17 commits in the last 90 days. Inferred · not functionally tested: Among its 6 catalogued features are AWS IAM Analysis, SMT Reasoning, and Access Proofs.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- AWS IAM Analysis
- SMT Reasoning
- Access Proofs
- Witness Generation
- Privilege Escalation Detection
- AI Agent Analysis
Topics: Inferred · not functionally tested
Built with & integrations
- Claude Code
- commit 9d5c18e77abf · since Oct 2026
Trust & compliance
Indexing history
2What PulseGate has recorded for this listing
- Indexed11 Oct · 15:22 UTCreach-security seen via PyPI Bulk EnumeratorSource: PyPI Bulk Enumerator · Open
Frequently asked questions about reach-security
- What does reach-security do?
- Inferred · not functionally tested: Reach-security focuses on determining and proving which AWS resources cloud credentials and AI agents can reach, including privilege-escalation paths. It is catalogued under AI & LLM security on PulseGate.
- Who is reach-security for?
- Inferred · not functionally tested: reach-security is an open-source project built for cloud security engineers and developers auditing AWS IAM permissions.
- Is reach-security free?
- Basis unknown · not verified: Yes — reach-security is open source under the AGPL-3.0 license and free to use.
- What platforms does reach-security run on?
- Basis unknown · not verified: reach-security runs on the command line. It can also be self-hosted.
- Is reach-security still active?
- The GitHub repository shows 17 commits in the last 90 days.
- What projects are similar to reach-security?
- Similar projects tracked by PulseGate include bawbel-gate, mcp-runtime-audit, and hypothesise.bawbel-gatemcp-runtime-audithypothesise
- Who develops reach-security?
- reach-security is developed by ctrl-adam.
- How long has reach-security been around?
- reach-security first shipped in 2026.
Also in AI & LLM security
Same category — not a similarity match