Users want to quickly capture and save downloadable web resources (videos, documents, archives, torrents, cloud links) directly to Quark Cloud Drive without manual downloading and re-uploading

User browses any webpage → content script (sniff.js + qk-content.js) scans the page DOM for video elements, links, and embedded resources → categorizes resources by type → displays detected resources in popup UI → user clicks save → extension communicates with Quark desktop client via nativeMessaging or direct API calls to pan.quark.cn/drive.quark.cn to save the resource to the user's Quark Cloud Drive

Target users: Quark Cloud Drive users / Users who frequently save web content (videos, documents, files) to cloud storage / Chinese internet users using Quark ecosystem

Source code is heavily minified/webpack-bundled making it difficult to trace exact login flow and API calls
Cannot definitively determine if the extension shows its own login UI or relies entirely on Quark desktop client authentication
Cannot verify whether saving to Quark Drive works without the desktop client installed

Monetization

No paid features detected

No evidence of payment UI, subscription APIs, Stripe/billing integrations, or feature gating in the extension code. All 'paid' keyword matches are false positives: 'pro' appears in webpack minified bundle variable names, 'license' in third-party LICENSE.txt files (MIT/BSD), and 'upgrade' is part of 'upgrade-insecure-requests' Content-Security-Policy directive. The extension itself is free and does not gate any features behind payment.

Confidence: 80
Payment platform: --
Source: AI / Medium
Login required: Yes
Reason: The extension's core workflow is sniffing web resources and saving them to Quark Cloud Drive (pan.quark.cn / drive.quark.cn). It requests 'cookies' permission and connects to Quark domains, indicating it relies on the user's existing Quark Cloud Drive session. The 'nativeMessaging' permission suggests communication with the Quark desktop client which holds the user's authenticated session. The extension itself does not implement its own login UI — it depends on the user being logged into the Quark service (via desktop client or web).

Permission risk

High-risk permissions

This estimate uses declared permissions and host permissions to assess access scope and sensitivity.

敏感权限：nativeMessaging、proxy
扩展能力较强：webRequest、storage、downloads、cookies、tabs
主机权限覆盖范围较宽
同时具备浏览数据与站点访问能力

Publisher

广州市动悦信息技术有限公司

Independent publisher

Email: [email protected]
Phone: --
Address: --

Public contact fields are shown above. Developer portfolio pages are available on paid accounts.

View developer portfolio

Permissions

Host access