Is Porto - Import Tweets to Bluesky safe?
Porto sends tweet archive link URLs to third-party preview and proxy services while building Bluesky embeds.
When you import a Twitter archive, Porto parses it locally but sends URLs found in tweets to noembed.com and api.allorigins.win to create link previews and fetch thumbnail data. When compressing an image, its worker imports image-compression code from cdn.jsdelivr.net at runtime, and that code runs in the worker that receives the selected image blob.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
What it can do
Permissions this extension asks for, as declared in version 1.2.9. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Sign you in with your Google account
identity
Where it sends data
Destinations our analysis observed Porto - Import Tweets to Bluesky 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.
- cdn.jsdelivr.netwidely used
Porto - Import Tweets to Bluesky sends data to cdn.jsdelivr.net. A widely used service: 32 other extensions we have analysed send data here.
- api.allorigins.win
Porto - Import Tweets to Bluesky sends data to api.allorigins.win. 3 other extensions we have analysed send data here.
- noembed.com
Porto - Import Tweets to Bluesky sends data to noembed.com. One other extension we have analysed sends data here.