{"version":"2.1.251","anchor":"better-detection-of-secrets-when-redacting-environment-value","canonical_anchor":"better-detection-of-secrets-when-redacting-environment-value","heading":"Better detection of secrets when redacting environment values","tier":"notice","area":"Privacy","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/better-detection-of-secrets-when-redacting-environment-value","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Better detection of secrets when redacting environment values\n\nEnvironment values that look like tokens are redacted much more reliably now.\n\n**What**\n\nThe check that decides whether a value looks like a secret, used to redact environment variables before they are recorded, now recognizes common token prefixes including `ghp_`-style GitHub tokens, `github_pat_`, `glpat-`, Slack `xox` tokens, `sk-`, `pk-`, `AKIA`, JWTs starting `eyJ`, `ya29.` and `npm_`, plus any string of 20 characters or more mixing letters and digits. It replaces a much narrower earlier scheme.\n\n**Evidence**\n\n`gh[opusr]_|github_pat_|glpat-|xox[abpr]-|sk-|pk-|AKIA|eyJ|ya29`\n\n- Area: Privacy\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}