{"version":"2.1.268","anchor":"bash-static-analysis-results-now-flag-whether-argv-came-pure","canonical_anchor":"bash-static-analysis-results-now-flag-whether-argv-came-pure","heading":"Bash static-analysis results now flag whether argv came purely from literals","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/bash-static-analysis-results-now-flag-whether-argv-came-pure","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Bash static-analysis results now flag whether argv came purely from literals\n\nBash permission checks now note whether a command's arguments came purely from literal text\n\n**What**\n\nWhen Claude Code statically analyzes a bash command to decide on permissions, its 'simple command' parsing result now includes two new fields: `argvSourceLiteral`, which indicates whether all the command's arguments came purely from literal text, and `carveOutMayDesyncQuoteScan`. Both are computed from counters that increase whenever the parser encounters arithmetic expansion, simple expansion, or herestring redirects (shell features that compute or substitute values rather than using plain text).\n\n**Why**\n\nThis gives the permission-checking logic more precise information about whether a command's arguments are trustworthy literal text or come from potentially dynamic shell expansions, which affects how safely the command's permissions can be evaluated.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}