apm deny
Synopsis
Section titled “Synopsis”apm deny [OPTIONS] PACKAGES...Description
Section titled “Description”apm deny blocks executable primitives from one or more dependency packages.
By default, it writes the decision to the project’s committed
apm.yml under executables.deny. Pass --user to write a machine-local
decision to ~/.apm/config.json instead. Run the command from an APM project:
an apm.yml file is required for both scopes.
A deny takes precedence over an allow. For the full precedence model and the
executable types covered by the gate, see
apm approve — Precedence.
Arguments and options
Section titled “Arguments and options”| Argument or flag | Description |
|---|---|
PACKAGES... | One or more package references, such as owner/repo. Required. |
--user | Record the deny in ~/.apm/config.json instead of apm.yml. |
For an installed package that declares executable types, APM records those types. When no executable declaration is found — because the package is not installed or declares no executables — APM blocks all supported executable types for that reference. Writing a deny also removes a matching allow from the selected store.
Examples
Section titled “Examples”Block a package for everyone using the project:
apm deny owner/repoBlock multiple packages:
apm deny owner/first owner/secondBlock a package only on the current machine:
apm deny --user owner/repoRelated
Section titled “Related”apm approve— Precedence — manage executable trust and inspect the deny-wins precedence model.apm policy— explain the effective trust decision for an installed package.apm install— install dependencies while enforcing the executable gate.