{"version":"2.1.232","anchor":"plugin-names-are-sanitized-before-appearing-in-failure-messa","canonical_anchor":"plugin-names-are-sanitized-before-appearing-in-failure-messa","heading":"Plugin names are sanitized before appearing in failure messages","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/plugin-names-are-sanitized-before-appearing-in-failure-messa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Plugin names are sanitized before appearing in failure messages\n\nA hostile plugin name can no longer inject escape codes into failure messages in your terminal.\n\n**What**\n\nThe summary that lists up to two failed plugins with `s.reason || s.error || \"unknown error\"` now strips control and bidirectional-text characters from each plugin name and truncates it at 200 characters, so a hostile name cannot inject terminal escape sequences.\n\n**Details**\n\n- A related plugin path helper gained a `PathUnverifiableError` class carrying a `code`.\n\n**Evidence**\n\n`unknown error`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}