{"version":"2.1.246","anchor":"commands-named-after-javascript-built-ins-no-longer-confuse-","canonical_anchor":"commands-named-after-javascript-built-ins-no-longer-confuse-","heading":"Commands named after JavaScript built-ins no longer confuse permission checks","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/commands-named-after-javascript-built-ins-no-longer-confuse-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Commands named after JavaScript built-ins no longer confuse permission checks\n\nCommands literally named constructor or __proto__ no longer skew Bash permission checks.\n\n**What**\n\nBash and PowerShell permission checking looked commands up in its tables by direct property access, so a command literally named `constructor` or `__proto__` matched a built-in language property instead of missing. Lookups now go through a safe helper, so such names can no longer skew write detection or argument skipping.\n\n**Details**\n\n- The affected tables are the ones listing command wrappers, options and verbs used to work out whether a command writes and which arguments to ignore.\n- A write with no determinable target still falls back to asking you: `is a write operation but no target path could be determined; requires manual approval`.\n\n**Evidence**\n\n`is a write operation but no target path could be determined; requires manual approval`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}