Skip to content

ExactGround v0.1.2 — security fixes

Choose a tag to compare

View all tags
@alidaram99 alidaram99 released this 03 Oct 07:00
· 5 commits to main since this release
v0.1.2
4a63f55

Security release. It fixes the findings of an independent review. Upgrade from v0.1.0/v0.1.1.

  • The agent can no longer approve its own install (high).
    • Hooks re-check the registry for every install and never allow from the local cache.
    • Strict mode is the hook default, so an unreachable registry means deny.
    • A project .exactground.json counts only after you run exactground trust, which records its SHA-256 outside the project. Any edit needs approval again.
    • Tool calls that write .exactground.json, the approvals or the cache are denied.
  • Fails closed. If the hook itself errors, the action is denied (EXACTGROUND_FAIL_OPEN=1 to opt out). Installs hidden in node -e, python -c, $(...) or eval are denied, because they cannot be checked.
  • pip install -r files must be regular files inside the project (no symlinks, at most 256 KB). Anything else denies the install.
  • Fix: scoped npm names are encoded for the downloads API.
  • Docs:
    • The limits are on the first screen.
    • The quickstart is pinned: npx -y github:alidaram99/exactground#v0.1.2.
    • The hosted API is marked as awaiting Apify Store publication.
  • Tests: 36 offline tests (8 new security regression tests); CI green on Windows and Linux with Node 20 and 24.

Install: claude plugin marketplace add alidaram99/exactground · codex plugin marketplace add alidaram99/exactground --ref v0.1.2 · gemini extensions install https://github.com/alidaram99/exactground --ref v0.1.2

Assets 2
Loading