{"version":"2.1.277","anchor":"hook-execution-supports-an-injected-sandboxexec-wrapper","canonical_anchor":"hook-execution-supports-an-injected-sandboxexec-wrapper","heading":"Hook execution supports an injected sandbox\/exec wrapper","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/hook-execution-supports-an-injected-sandboxexec-wrapper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Hook execution supports an injected sandbox\/exec wrapper\n\nHook commands can now optionally be run through a sandboxed execution wrapper before they start\n\n**What**\n\nThe internal function that runs hook commands now accepts an extra parameter that can optionally acquire a sandboxed executable resource before starting the hook process. If that sandboxed resource can't be obtained, the hook is now treated as having failed to spawn, rather than running normally.\n\n**Why**\n\nThis lets hook commands be run inside a sandbox when needed, and ensures that if the sandbox can't be set up, the hook fails safely instead of running outside the sandbox unexpectedly.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}