Twitter Video Downloader – ClipSave extension
Security at a glance
Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportChrome listing ID: njlhfhignlajkblipljhjlaleoffooic
Permissions (4)
- Execute scripts in pages
- Manage downloads
Related extensions
xSave - the best X (Twitter) Video Downloader for ChromeLifestyle
X (Twitter) Video Saver - One Click X / Twitter Video DownloaderLifestyle
X (Twitter) Video Saver - Twitter Video DownloaderSocial & Communication
Twitter Video Downloader – Save X HD & GIFLifestyle
Twitter Video Downloader – ClipSavePhotos
X Video Downloader – ClipSaveDownload Management
Frequently asked questions
Is Twitter Video Downloader – ClipSave safe to use?
Our latest automated scan rates the Chrome listing of Twitter Video Downloader – ClipSave at 80/100 (some risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does Twitter Video Downloader – ClipSave require?
Twitter Video Downloader – ClipSave requests 4 permissions. The most significant: Execute scripts in pages, Manage downloads. See the full breakdown in the security report.
Who develops Twitter Video Downloader – ClipSave?
Twitter Video Downloader – ClipSave is published by a38395858. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Chrome
- Checked version
- Not provided in this assessment
- Current listed version
- 1.1.2
- Assessment updated (UTC)
- Assessment status
- Completed
Recorded findings: 0 critical and 1 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.