Is Control for Transmission safe?
Control for Transmission sends Basic Auth credentials to user-configured Transmission RPC endpoints over HTTP.
When a user configures a Transmission RPC URL with HTTP and enables authentication, the extension sends RPC POST requests with an Authorization: Basic header containing the configured username and password. This can happen while testing the connection, opening the popup, or adding a torrent; HTTPS RPC URLs are not affected by the cleartext transport issue.
Who publishes itJackie(Guokai) Han - 5 other listings from the same operator, none carrying a finding
Jackie(Guokai) Han - 5 other listings from the same operator, none carrying a finding
What this publisher told the store about itself, and the other listings that told it the same thing.
Same store account
5 other listings published from this account, 304k+ users between them, none of them carrying a finding.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
Where it sends data
Destinations our analysis observed Control for Transmission contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- user-configured Transmission RPC endpoint
Control for Transmission sends data to user-configured Transmission RPC endpoint. Named as a recipient in this extension's own analysis.