{"version":"2.1.228","anchor":"plugin-in-use-markers-get-their-own-directory-and-escape-che","canonical_anchor":"plugin-in-use-markers-get-their-own-directory-and-escape-che","heading":"Plugin in-use markers get their own directory and escape checks","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/plugin-in-use-markers-get-their-own-directory-and-escape-che","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Plugin in-use markers get their own directory and escape checks\n\nPlugin in-use markers now live in their own folder and cannot escape the plugins directory.\n\n**What**\n\nThe per-process marker that records a linked plugin as in use is now written under a dedicated `.in_use-links` directory whose resolved path must stay inside the plugins directory.\n\n**Details**\n\n- Each path component is created and re-resolved against the real filesystem path; if any step resolves outside, the marker is not written and the scan is skipped, with a log naming the offending path.\n\n**Evidence**\n\n`.in_use-links`\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}