Netlify command protection
Reviews site deletion and production deployments.
Evidence at a glance
- Source
- Merged native coverage · f440ae1a9f
- Activation
- This coverage is built into the native Guard runtime.
- Maintainer
- Project maintained
- Coverage
- 2 rules · 2 permissions
Coverage and limits
Reviews site deletion and production deployments.
- 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 and enforcement
How Guard maps this extension onto your workspace policy: which commands it recognizes, which tools it touches, and how each tool state resolves.
Runtime identity
- Catalog ID
command.platform.netlify- Guard enforcement ID
command.platform.netlify- Source path
src/codex_plugin_scanner/guard/runtime/command_builtin_extension_registry.py
Tool state mapping
No per-tool overrides are declared. Every tool this extension touches resolves through the workspace Guard policy as-is.
Action classes
Netlify destructive commandNetlify production commandFrequently asked questions
What does Netlify command protection cover?
Reviews site deletion and production deployments. The listing declares 2 rules and 2 permission checks. Coverage is limited to these reviewed operations and the surrounding Guard policy.
Is Netlify command protection active by default?
Built-in coverage: This coverage is built into the native Guard runtime. Enabling state is always controlled through Guard policy, never from this directory.
Who maintains Netlify command protection?
This listing is maintained by the HOL Guard project itself as part of the native runtime catalog.
Is a listing of Netlify command protection a security guarantee?
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.