CLIHarbor
An open-source Windows-first local browser UI for safely exposing curated workflows from official command-line tools through trusted packs, deterministic argv planning, bounded execution, and explicit vendor-owned authentication.
Quick Facts
- Platform
- Windows
- Purchase model
- Free & open source
Key Features
- Run a loopback-only local browser UI backed by an authenticated local API rather than a remotely exposed multi-user service
- Load reviewed trusted packs that map typed browser inputs to deterministic executable + argv arrays without arbitrary shell strings
- Discover exact Windows executables, reject ambiguous or incompatible candidates, and revalidate executable identity before execution
- Use bounded process timeout, output, cancellation, Windows Job Object lifecycle containment, and privacy-preserving diagnostics
- Ship a qualified Windows evaluation flow with preflight evidence and a zero-config embedded Conjur 9.x pack
- Provide reviewed read-only CyberArk/Idira Conjur 9.x workflows while leaving credential entry and vendor session ownership to Conjur
- Optionally install one exact pinned and SHA-256-verified Conjur CLI into the current user cache when the CLI is genuinely missing, without requiring administrator credentials
- Keep secret-returning, destructive, unreviewed generated-command, and CLIHarbor-owned credential workflows intentionally gated
Frequently Asked Questions
Does CLIHarbor require administrator credentials?
The normal evaluation path is designed for the current Windows user and does not intentionally request elevation, write Program Files, change machine PATH, install services, or bypass enterprise controls.
Does CLIHarbor execute arbitrary shell commands?
No. Normal tasks are defined by reviewed trusted packs and execute an exact executable with a deterministic argv array. The browser cannot supply raw shell strings or arbitrary argv.
Does CLIHarbor store Conjur credentials?
No. Vendor authentication remains vendor-owned. CLIHarbor does not implement its own username/password/MFA forms or persist vendor credentials.
Where can I get CLIHarbor?
CLIHarbor is open source on GitHub. Qualified Windows evaluation artifacts are produced by successful main-branch CI runs and should be checked with the bundled preflight before use.
Help & feedback
Report a problem, suggest an improvement, or contact the developer about CLIHarbor. No GitHub account is required.