PHP package protection
Routes Composer dependency operations through Guard's package firewall.
command.package.php · v1.0.0 · Package supply chain
- Protection rules
- 0
- Permission checks
- 1
- Mapped commands
- 1
Overview
What this coverage does
Routes Composer dependency operations through Guard's package firewall.
Key facts
- Catalog ID
command.package.php- Version
- v1.0.0
- Kind
- Command coverage
- Category
- Package supply chain
- Protection rules
- 0
- Permission checks
- 1
- Mapped commands
- 1
- Maintainer
- HOL Guard Team(project-maintained)
- Source commit
- ff3d4eb
- Protection model
- Package firewall
Coverage is delegated to Guard package-firewall controls.
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.
No per-command matchers are published for this listing. Coverage is described by the reviewed rule count, permission checks, and the surrounding Guard policy.
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.package.php
- Guard enforcement ID
- command.package.php
- Source path
- contributions/extensions/command.package.php.json
- Contribution digest
sha256…a8ea7c
Mapped executables
composerTechnical 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
Routes Composer dependency operations through Guard's package firewall. The listing declares 0 rules and 1 permission check. No per-command matchers are published for this listing.. Coverage is limited to these reviewed operations and the surrounding Guard policy.
Package firewall: Coverage is delegated to Guard package-firewall controls. Enabling state is always controlled through Guard policy, never from this directory.
This listing is maintained by the HOL Guard project itself as part of the native runtime catalog.
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.
This listing does not publish per-command matchers. Exact behavior follows your Guard policy combined with this entry's 0 rules and 1 permission check.
Coverage is delegated to Guard package-firewall controls. 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.package.php 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 0 rules and 1 permission check.
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 coverage is accepted through public pull requests with recorded provenance. Project-maintained listings like this one are extended by the HOL Guard team; propose new operations through the hol-guard repository.
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.