{"version":"2.1.222","anchor":"unsafe-path-command-resolution-guard-off-in-this-build","canonical_anchor":"unsafe-path-command-resolution-guard-off-in-this-build","heading":"Unsafe-PATH command resolution guard, off in this build","tier":"soon","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/unsafe-path-command-resolution-guard-off-in-this-build","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Unsafe-PATH command resolution guard, off in this build\n\nA guard that would reject commands found only in your current directory stays disabled.\n\n**What**\n\nA third spawn wrapper picked up the same guard as the other two: resolve the command and refuse it if it only resolves inside the current directory.\n\n**Details**\n\n- The predicate that controls all three call paths is a function that returns false in this build, so no command is refused at runtime.\n- If enabled, a command found only in the current directory would be rejected as being in an unsafe location.\n\n**Evidence**\n\n`not found or is in an unsafe location (current directory)`\n\n- Area: Sandbox\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}