Package supply chainCommand contributionv1.0.0Package firewall

Rust package protection

Routes Cargo dependency and binary installation requests through Guard's package firewall.

Claim publisher pageView exact source Documentation

Evidence at a glance

Source
Merged native coverage · f440ae1a9f
Activation
Coverage is delegated to Guard package-firewall controls.
Maintainer
Project maintained
Coverage
0 rules · 1 permissions · 1 mapped command

Coverage and limits

Routes Cargo dependency and binary installation requests through Guard's package firewall.

  • 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.

0
Reviewed rules
1
Permission checks
0
Per-tool overrides
v1.0.0
Listing version

Runtime identity

Catalog ID
command.package.rust
Guard enforcement ID
command.package.rust
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.

Mapped commands and executables

cargo

Frequently asked questions

What does Rust package protection cover?

Routes Cargo dependency and binary installation requests through Guard's package firewall. The listing declares 0 rules and 1 permission check. Coverage is limited to these reviewed operations and the surrounding Guard policy.

Is Rust package protection active by default?

Package firewall: Coverage is delegated to Guard package-firewall controls. Enabling state is always controlled through Guard policy, never from this directory.

Who maintains Rust package protection?

This listing is maintained by the HOL Guard project itself as part of the native runtime catalog.

Is a listing of Rust package 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.