D

drip command protection

Reviews drip runs that change local setup (install), write the token ledger (sync) or launch another command (run), and keeps the read-only

Reviews drip runs that change local setup (install), write the token ledger (sync) or launch another command (run), and keeps the read-only views (statusline, session, history, explain, open, splash, watch) unreviewed.

command.drip · v1.0.0 · Other extensions

By Community contributorExternal · opt-inCommand coverage
Try this coverage Install GuardView exact source drip command protection documentation Claim this coverage
0
Protection rules
3
Permission checks
3
Mapped commands
3

Overview

What this coverage does

Reviews drip runs that change local setup (install), write the token ledger (sync) or launch another command (run), and keeps the read-only views (statusline, session, history, explain, open, splash, watch) unreviewed.

Key facts

Catalog ID
command.drip
Version
v1.0.0
Kind
Command coverage
Category
Other extensions
Protection rules
3
Permission checks
3
Mapped commands
3
Maintainer
Community contributor(community, provenance recorded)
Source commit
d39149a
Protection model
External · opt-in
External · opt-in

External coverage. It must be enabled through Guard controls; this page does not activate it.

Stated limits

  • Coverage is limited to the reviewed operations and the surrounding Guard policy.
  • A maintainer profile is not a security certification or an official upstream endorsement.

Command mapping

Every command this extension recognizes, with the catalog default floor Guard applies before workspace policy. Search the table, then open an operation for safe variants and the permission ID.

3 operations · 3 reviewed by default These are catalog defaults, not your workspace policy.

3 operations3 reviewed
Default floor

Showing 3 of 3 operations

  • Reviewed Guard intercepts the command for review before it runs.High
    • drip run codex
    drip agent launch
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies `drip run <command>`, which resolves the given command on PATH or a known install location and replaces itself with it, after opening a meter pane through tmux, Ghostty or iTerm2 AppleScript, a Warp tab config (written to ~/.warp/tab_configs), or a separate Terminal window. Any command can follow `run`, so it is reviewed as execution.
    Permission ID
    command.drip.permission.run
  • Reviewed Guard intercepts the command for review before it runs.Medium
    • drip install
    drip setup
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies `drip install`, which imports Claude Code and Codex history into the local ledger (~/.local/share/drip/usage.db), symlinks bin/drip into ~/.local/bin, and adds a statusLine command to ~/.claude/settings.json when none is set, so Claude Code runs drip on every status-line refresh. Without a TTY (for example from an agent) it also opens a new terminal window to play its intro. It has no…
    Permission ID
    command.drip.permission.install
  • Reviewed Guard intercepts the command for review before it runs.Low
    • drip sync
    drip ledger import
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies `drip sync`, which reads every Claude Code transcript under ~/.claude/projects and Codex rollout under ~/.codex/sessions and writes new token counts and file offsets into the local ledger (~/.local/share/drip/usage.db). It has no preview form.
    Permission ID
    command.drip.permission.sync

Tool state mapping

No per-tool overrides are declared. Command defaults above resolve through the workspace Guard policy unless a later policy layer changes them.

Runtime identity

Catalog ID
command.drip
Guard enforcement ID
command.drip
Source path
contributions/extensions/command.drip.json
Contribution digest
sha256…a05126

Action classes

drip setup commanddrip ledger import commanddrip agent launch command

Technical profile

No independent profile published

This extension has no current independent technical profile. Catalog facts and any legacy launch remain separate and are not presented as profile evidence.

FAQ

Frequently asked questions

Reviews drip runs that change local setup (install), write the token ledger (sync) or launch another command (run), and keeps the read-only views (statusline, session, history, explain, open, splash, watch) unreviewed. The listing declares 3 rules and 3 permission checks. 3 operations · 3 reviewed by default. Coverage is limited to these reviewed operations and the surrounding Guard policy.

External · opt-in: External coverage. It must be enabled through Guard controls; this page does not activate it. Enabling state is always controlled through Guard policy, never from this directory.

This listing entered the catalog as a community contribution through a public pull request with recorded provenance, with public credit to @beausterling, and 1 GitHub maintainer is recorded on the listing. Credit is attribution only. A verified publisher profile and the claim flow verify authority separately; neither is an upstream endorsement or a HOL safety certification.

No. Every listing documents source, activation model, maintainer identity, and stated limitations so you can evaluate coverage before enabling it. Review the stated limitations and the exact source tree before relying on any single control.

3 operations · 3 reviewed by default. Examples: drip run codex (reviewed by default); drip install (reviewed by default); drip sync (reviewed by default). These are catalog defaults, not your workspace policy.

External coverage. It must be enabled through Guard controls; this page does not activate it. Enablement is managed through your workspace's Guard policy and controls — never from this directory. Open the install guidance for the setup flow, then adjust the command coverage for command.drip in Guard's policy surface.

The matching action is stopped at Guard's pre-action boundary before it executes, and the decision is recorded with evidence your workspace can review. Exact behavior follows your Guard policy combined with this entry's 3 rules and 3 permission checks.

No. Guard is local-first: interception, decisions, and evidence stay on your machine unless your workspace explicitly configures cloud features. This page is documentation only — it never executes a command or changes protection state.

Guard runs locally alongside the major AI coding agents and MCP-capable harnesses, so this coverage applies wherever Guard intercepts actions. See the supported harness guides at https://hol.org/guard/harnesses for per-tool approval behavior and limitations.

Guard has a free local tier that includes command interception, evidence, and the policy controls this listing documents. Team plans add shared policy, review queues, and audit surfaces. Current plans: https://hol.org/guard/pricing

Open an issue or pull request against the hol-guard repository, where the canonical catalog lives: https://github.com/hashgraph-online/hol-guard Listings are corrected through the same public review process that adds them.

Yes. Community extensions are merged through public pull requests with recorded provenance, and you can claim the publisher page for a contribution you maintain through the Publisher Studio.

The command mapping table is the audit trail for covered commands and catalog default floors. Pair it with the reviewed rule and permission counts, the per-tool state mapping, and the exact source tree linked from View exact source at the reviewed commit. Guard records enforcement decisions with evidence locally, so what ships matches what you reviewed.