Require trusted metadata for non-default DMG sources

[nisavid]

Summary

Require trusted metadata or explicit developer-mode handling for non-default remote DMG sources.

Source

Migrated from docs/maintainers/security-backlog.md.

Maintained Docs

• Security backlog index and review workflow: docs/maintainers/security-backlog.md
• Threat model: docs/maintainers/threat-model.md
• Package and runtime maintenance: docs/maintainers/package-runtime-maintenance.md

Context

Runtime config can redirect dmg_url for development and testing. URL parsing rejects userinfo and non-HTTPS non-loopback URLs, but non-default remote sources are still supply-chain inputs.

Review Gate

Run the @codex-security workflow before treating implementation as review-ready.

Desired State

• Non-default remote dmg_url values require the same trusted metadata or explicit developer-mode handling as the default update channel.
• Logs identify non-default update hosts without persisting secrets.

[coderabbitai]

🔗 Related PRs

#4 - Security hardening and release verification [merged]
#6 - docs(security): persist Apple DMG verification evidence [merged]
#47 - chore(sync): merge upstream main [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!