Responsive Studio — Trình Giả Lập Đa Thiết Bị Web 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: eclbnfenoalamefdbocdhnkekmgfmjmi
Permissions (10)
- Browser debugger access
- View open tabs
- Execute scripts in pages
Related extensions
Mobile Simulator & Responsive Tester ToolsProductivity
Responsive Simulator - Multi Device Viewport TesterProductivity
Mobile Simulator (Self-Hosted)Productivity
Responsive Tester - Multi-Screen SimulatorProductivity
Multi Device Simulator — Mobile Responsive Testing & RecordingProductivity
Responsive Viewer — Mobile & Tablet SimulatorProductivity
Frequently asked questions
Is Responsive Studio — Trình Giả Lập Đa Thiết Bị Web safe to use?
Our latest automated scan rates the Chrome listing of Responsive Studio — Trình Giả Lập Đa Thiết Bị Web at 78/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 Responsive Studio — Trình Giả Lập Đa Thiết Bị Web require?
Responsive Studio — Trình Giả Lập Đa Thiết Bị Web requests 10 permissions. The most significant: Browser debugger access, View open tabs, Execute scripts in pages. See the full breakdown in the security report.
Who develops Responsive Studio — Trình Giả Lập Đa Thiết Bị Web?
Responsive Studio — Trình Giả Lập Đa Thiết Bị Web is published by luongthanhtunglc. 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
- 2.2.5
- Current listed version
- 2.2.5
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 3 critical and 39 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.