HASP addresses the critical security vulnerability of exposing sensitive credentials to coding agents. It acts as a local-first secret broker, safeguarding secrets within an encrypted vault and delivering them only at runtime, thereby preventing them from entering agent context. This enhances trust and security for developers and researchers utilizing agent workflows that require access to APIs, test environments, or deployment pipelines.

How It Works

HASP employs a local encrypted vault to store secrets. Its core mechanism involves brokering access to these secrets for commands and agent tooling. By materializing plaintext secrets only when explicitly requested by an operator at runtime, HASP ensures that sensitive values are never exposed within the agent's operational context. This approach prioritizes security and avoids the need for a hosted control plane in its v1 architecture.

Quick Start & Requirements

• Installation: macOS/Linux users can install via Homebrew (brew tap gethasp/tap && brew install gethasp/tap/hasp). Source builds require make build.
• Setup: A guided setup is initiated with hasp setup.
• Documentation: Detailed guides for installation, upgrades, first-run paths, and operational models are available in install.md, QUICKSTART.md, and mental-model.md.

Highlighted Details

• Manages secrets in a local encrypted vault.
• Brokers secret access to commands and agent tooling.
• Supports run, inject, MCP, and app connection flows.
• Integrates repo hooks to prevent managed secrets from being committed or deployed.
• Maintains audit records for all brokered secret usage.
• Telemetry is opt-in by default.
• Provides first-class profiles for popular agents like Codex CLI, Claude Code, Cursor, and others.

Maintenance & Community

No specific details regarding community channels (e.g., Discord, Slack), notable contributors, sponsorships, or roadmap were found in the provided README.

Licensing & Compatibility

HASP is distributed under the Fair Core License. This source-available license may impose restrictions on usage, particularly concerning commercial applications or closed-source linking, which are not detailed within the README.

Limitations & Caveats

The project is described as "local-first" and focuses on "v1," suggesting its current scope is primarily for local development environments and may evolve. The specific implications of the Fair Core License for broader compatibility are not elaborated upon in the README.