{"version":"2.1.296","anchor":"secret-scanner-sensitive-assign-and-cloud-env-var-patterns-m","canonical_anchor":"secret-scanner-sensitive-assign-and-cloud-env-var-patterns-m","heading":"Two low-confidence secret-scanner rules now use prebuilt patterns","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/secret-scanner-sensitive-assign-and-cloud-env-var-patterns-m","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Two low-confidence secret-scanner rules now use prebuilt patterns\n\nTwo low-confidence secret-scanner rules now load prebuilt search patterns instead of building them in place\n\n**Unclear.** It is not clear whether the patterns themselves changed, so whether these rules now flag different text is unknown.\n\n**What**\n\nClaude Code has a secret scanner, a check that looks through text for things such as passwords, keys or tokens. Two of its rules are marked low-confidence, meaning a match is a weaker sign of a real secret. They now load ready-made search patterns instead of building their patterns in place:\n\n- the rule for sensitive-looking values assigned to a name (`sensitive-assign`)\n\n- the rule for cloud environment variables\n\n**Why**\n\nThis looks like a tidy-up of how the patterns are stored. If the patterns themselves differ, what these two rules flag may differ too.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}