Guided first use
Try rls-saboteur command protection
Reviews rls-saboteur runs. It reads the source database read-only, creates temporary labelled copies of it on the same server, breaks polici Follow the three steps below with your own setup — nothing on this page runs on your machine or changes a policy.
Step 1 · Check fit
What this coverage governs
Reviews rls-saboteur runs. It reads the source database read-only, creates temporary labelled copies of it on the same server, breaks policies only in those copies, and drops them. Also reviews the flags that let it run against a non-local database, terminate other sessions on the source, or leave outbound HTTP on in the copies. Direct runs with --help, -h, --version, -v, --dry-run or --checks-only are not matched (launcher forms stay in review). Covers the rls-saboteur executable and npx, bunx, pnpx, pnpm, yarn, npm exec, npm x, bun x, pnpm dlx and yarn dlx launches, including versioned launches (rls-saboteur@tag).
External — off until you opt in
This coverage stays off until you explicitly enable it from your Guard workspace controls. Reading this page never changes your policy; activation happens in Guard itself.
Harness support
No harness compatibility profile is published yet. Check the Guard harness guide for what your setup uses.
Are you the publisher? Complete this section in your Studio — until then this stays unknown for readers instead of being guessed.
Catalog version 1.0.0 · source snapshot 52dd51096a
Step 2 · Set up
Install and activate
No reviewed setup steps are published for this coverage yet. Install Guard itself, then return here after the publisher publishes a guide — or ask for one. Are you the publisher? Complete this section in your Studio.
New to Guard? Start with Install Guard. Already installed? Skip install — this coverage stays off until you enable it from your workspace controls.
Activation happens in your Guard workspace. This page links to it; it never enables the coverage for you.
Missing the setup information you need? Request setup documentation — the publisher reviews requests before anything is published here.
Step 3 · Verify the result
Run a safe test and compare
Safe fixture inputs
No published safe fixture yet. Try the coverage against a harmless command of your own — not production traffic.
Are you the publisher? Complete this section in your Studio — until then this stays unknown for readers instead of being guessed.
Expected outcome
No expected outcome published yet. Guard surfaces what it matched — the rule and its decision — in its own activity view; compare that with this coverage’s stated rules to inspect the actual decision.
Are you the publisher? Complete this section in your Studio — until then this stays unknown for readers instead of being guessed.
Outcome reporting
This coverage has no claimed publisher page yet, so outcome reports are not collected. You can still verify the result locally against the expected outcome above.