pyrig command protection
Reviews pyrig project initialization, synchronization, scratch execution, scaffolding, cache deletion, and integration removal. Covers direc
Reviews pyrig project initialization, synchronization, scratch execution, scaffolding, cache deletion, and integration removal. Covers direct pyrig entrypoints and uv run pyrig, not arbitrary project CLIs, plugin commands, or other launchers. Help and version do not match operation rules; independent Guard requirements still apply. Based on pyrig 18.99.1; installed plugins and overrides can change behavior.
command.pyrig · v1.0.0 · Other extensions
- Protection rules
- 8
- Permission checks
- 8
- Mapped commands
- 8
Overview
What this coverage does
Reviews pyrig project initialization, synchronization, scratch execution, scaffolding, cache deletion, and integration removal. Covers direct pyrig entrypoints and uv run pyrig, not arbitrary project CLIs, plugin commands, or other launchers. Help and version do not match operation rules; independent Guard requirements still apply. Based on pyrig 18.99.1; installed plugins and overrides can change behavior.
Key facts
- Catalog ID
command.pyrig- Version
- v1.0.0
- Kind
- Command coverage
- Category
- Other extensions
- Protection rules
- 8
- Permission checks
- 8
- Mapped commands
- 8
- Maintainer
- Community contributor(community, provenance recorded)
- Source commit
- 85c5e82
- Protection model
- 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.
8 operations · 8 reviewed by default These are catalog defaults, not your workspace policy.
Showing 8 of 8 operations
- Reviewed Guard intercepts the command for review before it runs.High
pyrig scratch
pyrig scratch execution
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Reviews execution of .scratch.py.
- Documented safe variants
Show scratch helpskip this operation when they are the documented preview or help form.- Permission ID
- command.pyrig.permission.execute-scratch
- Reviewed Guard intercepts the command for review before it runs.High
pyrig init
pyrig project initialization
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Reviews removal of managed configuration and initial project/Git setup.
- Documented safe variants
Show initialization helpskip this operation when they are the documented preview or help form.- Permission ID
- command.pyrig.permission.initialize
- Reviewed Guard intercepts the command for review before it runs.High
pyrig rm pyrig
pyrig integration removal
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Reviews hook and development dependency removal.
- Documented safe variants
Show integration removal helpskip this operation when they are the documented preview or help form.- Permission ID
- command.pyrig.permission.remove-integration
- Reviewed Guard intercepts the command for review before it runs.Medium
pyrig mk cmd example --shared
pyrig command scaffolding
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Reviews writes to project and shared CLI modules.
- Documented safe variants
Show command scaffolding helpskip this operation when they are the documented preview or help form.- Permission ID
- command.pyrig.permission.scaffold-command
- Reviewed Guard intercepts the command for review before it runs.Medium
pyrig mk subcls pyrig.rig.tools.pyrigger Pyrigger
pyrig subclass scaffolding
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Reviews module imports and subclass source writes.
- Documented safe variants
Show subclass helpskip this operation when they are the documented preview or help form.- Permission ID
- command.pyrig.permission.scaffold-subclass
- Reviewed Guard intercepts the command for review before it runs.Medium
pyrig sync
pyrig project synchronization
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Reviews managed file updates and source imports for mirrored tests.
- Documented safe variants
Show synchronization helpskip this operation when they are the documented preview or help form.- Permission ID
- command.pyrig.permission.synchronize
- Reviewed Guard intercepts the command for review before it runs.Low
pyrig mk inits
pyrig initialization file creation
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Reviews creation of missing source/test __init__.py files.
- Documented safe variants
Show initialization file helpskip this operation when they are the documented preview or help form.- Permission ID
- command.pyrig.permission.create-init-files
- Reviewed Guard intercepts the command for review before it runs.Low
pyrig rm pyc
pyrig bytecode cache removal
- Default floor
- Reviewed by default. Guard intercepts the command for review before it runs.
- Detector mode
- review
- What it matches
- Reviews recursive deletion of source/test bytecode caches.
- Documented safe variants
Show cache cleanup helpskip this operation when they are the documented preview or help form.- Permission ID
- command.pyrig.permission.remove-bytecode
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.pyrig
- Guard enforcement ID
- command.pyrig
- Source path
- contributions/extensions/command.pyrig.json
- Contribution digest
sha256…37d3bd
Action classes
pyrig project initializationpyrig project synchronizationpyrig scratch executionpyrig source scaffoldingpyrig cache deletionpyrig integration removalTechnical 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 pyrig project initialization, synchronization, scratch execution, scaffolding, cache deletion, and integration removal. Covers direct pyrig entrypoints and uv run pyrig, not arbitrary project CLIs, plugin commands, or other launchers. Help and version do not match operation rules; independent Guard requirements still apply. Based on pyrig 18.99.1; installed plugins and overrides can change behavior. The listing declares 8 rules and 8 permission checks. 8 operations · 8 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. 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.
8 operations · 8 reviewed by default. Examples: pyrig scratch (reviewed by default); pyrig init (reviewed by default); pyrig rm pyrig (reviewed by default); pyrig mk cmd example --shared (reviewed by default); pyrig mk subcls pyrig.rig.tools.pyrigger Pyrigger (reviewed by default); pyrig sync (reviewed by default); pyrig mk inits (reviewed by default); pyrig rm pyc (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.pyrig 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 8 rules and 8 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.