{"version":"2.1.224","anchor":"plugins-can-be-installed-from-an-https-zip-archive","canonical_anchor":"plugins-can-be-installed-from-an-https-zip-archive","heading":"Plugins can be installed from an HTTPS zip archive","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/plugins-can-be-installed-from-an-https-zip-archive","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Plugins can be installed from an HTTPS zip archive\n\nZip plugin installs strip a single wrapping directory so the plugin lands at top level.\n\n**What**\n\nA marketplace entry can now point at a zip file over HTTPS instead of a git repo or npm package, with an optional sha256 digest that is checked on every download. When no version is declared, that digest is what identifies the version. If the zip contains a single wrapping directory, it is stripped so the plugin lands at the top level.\n\n**Details**\n\n- The URL is checked against a new guard that rejects loopback, link-local, IPv4-mapped IPv6, unique-local and cloud-metadata hosts, so a marketplace entry cannot make Claude Code fetch from inside your network.\n- Authentication headers are inherited from the enclosing url-sourced marketplace only when the origins match.\n- The error message for marketplaces configured in settings now lists this type alongside github, git-subdir, npm and url.\n\n**Evidence**\n\n`Archive URLs must use https:\/\/ and must not point at a loopback, link-local, or cloud-metadata host`\n\n- Area: Plugins\n- Names: `sha256`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}