The optional release fallback sends its configured Gitea token to an asset URL supplied by release metadata without checking the URL's origin. This is a credential-handling vulnerability requiring a configured fallback and an update attempt, so it warrants a warning rather than a malicious verdict.
Static reason
No blocking static signals were detected.
Trigger
A user runs the update command, npm lookup fails, and a Gitea fallback is configured with a token.
Impact
A manipulated or compromised release response could direct the request to another host and disclose the configured Gitea token.
Mechanism
The CLI takes browser_download_url from the configured Gitea release response and sends the Gitea authorization header with the asset request without checking that URL's origin.
Network endpoints2
Configured Gitea origin from DEVBOARD_RELEASE_URL, DEVBOARD_GITEA_URL, or GITEA_URL; release API path /api/v1/repos/{repo}/releases/...Release-supplied asset.browser_download_url; origin is not validated