{"version":"2.1.268","anchor":"artifacts-tool-tracks-unverified-path-spelling","canonical_anchor":"artifacts-tool-tracks-unverified-path-spelling","heading":"Artifacts tool tracks unverified path spelling","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/artifacts-tool-tracks-unverified-path-spelling","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Artifacts tool tracks unverified path spelling\n\nPublishing an artifact now checks its file path for disguised or lookalike spelling\n\n**What**\n\nWhen the artifacts tool resolves the file path for something being published, its result now includes a new `unverifiedSpelling` field alongside the existing pin and redirect information. This points to the same check for obfuscated or disguised path names already used elsewhere (such as when registering a repository root) now also being applied to files being published as artifacts.\n\n**Why**\n\nThis helps catch cases where a published artifact's path looks legitimate but uses a disguised spelling, closing a gap between two features that previously applied this check inconsistently.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}