essh
Reviews essh host group execution and removal of cached hosts, keys, and workspaces.
Evidence at a glance
- Source
- Merged native coverage · f440ae1a9f
- Activation
- External coverage. It must be enabled through Guard controls; this page does not activate it.
- Maintainer
- Publisher profile not claimed yet
- Coverage
- 2 rules · 2 permissions
Coverage and limits
Reviews essh host group execution and removal of cached hosts, keys, and workspaces.
- 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.remote.essh- Guard enforcement ID
command.remote.essh- Source path
contributions/extensions/command.remote.essh.json- Contribution digest
sha256:e7cea64f5372fcc2eac66470d2159e7d52d5572300e415897e89a97236225d7b
Tool state mapping
No per-tool overrides are declared. Every tool this extension touches resolves through the workspace Guard policy as-is.
Action classes
essh group execution commandessh cache removal commandFrequently asked questions
What does essh cover?
Reviews essh host group execution and removal of cached hosts, keys, and workspaces. The listing declares 2 rules and 2 permission checks. Coverage is limited to these reviewed operations and the surrounding Guard policy.
Is essh active by default?
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.
Who maintains essh?
This listing entered the catalog as a community contribution through a public pull request with recorded provenance. A verified publisher profile attributes the contributor; it is not an upstream endorsement or a HOL safety certification.
Is a listing of essh 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.