DWA Open Data · data APIs on Apify
DATA · Leads & companies

Chrome Extension Permissions Audit: Web Store Data

Search the Chrome Web Store by keyword, category or extension ID. Each row has users, rating, version, last updated, size, developer, trader status, plus the declared permissions, host access, Manifest V2/V3 and a low/medium/high permission risk tier.

Who it is for

Sales, growth and RevOps teams building prospect lists, and agencies feeding a CRM with fresh, structured company data.

Pricing

EventPricePer 1,000
ExtensionCharged once per extension row delivered to the dataset (after the featured, publisher, users, rating and risk filters). Extensions that were filtered out, not found or invalid are never charged.--
Actor StartCharged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).$0.00005-

Prices are read live from the Apify listing at build time. Apify platform usage is included in event prices.

Sample output

idnamedeveloperdeveloperWebsitetraderStatus
hdokiejnpimakedhajhdlcegeplioahdLastPass: Free Password ManagerLastPasstrader
caljgklbbfbcjjanaijlacgncafpegllAvira Password ManagerAviratrader
admmjipmmciaobhojoghlmleefbicajgNorton Password ManagerNortonLifeLock Inchttps://norton.com/non-trader

First rows of a real run, selected columns. Emails, phone numbers and personal names are masked. Full output has more fields.

Input

  • searchQueries · Search queries: Chrome Web Store searches, e.g. "password manager" or "ai writing". Results are taken in Store order.
  • categories · Categories: Store categories to list (the Store shows up to about 500 extensions per category).
  • extensionIds · Extension IDs or URLs: Extension ids (32 letters) or any Chrome Web Store URL: detail pages, search pages (/search/...) and category pages (/category/extensions/...).
  • maxItems · Max extensions: Stop after this many extension rows in total. You pay per extension delivered.
  • includeDetails · Include full details: Read each detail record for developer, trader status, last updated, size, languages, full description, support and privacy URLs. Off = listing data only (still includes permissions, users, rating and version).
  • featuredOnly · Featured only: Keep only extensions with the Featured badge.
  • establishedPublishersOnly · Established publishers only: Keep only extensions from publishers with the Established publisher badge.
  • minUsers · Minimum users: Skip extensions with fewer users (filtered before charging).
  • minRating · Minimum rating: Skip extensions rated below this (filtered before charging).
  • riskLevels · Permission risk levels: Keep only these risk tiers (empty = all). Example: high lists extensions that can read all websites or use high-impact APIs.

Use it from an AI agent (MCP)

Add this server URL to Claude, Cursor, VS Code or any MCP client. Authenticate with your Apify account.

https://mcp.apify.com/?tools=transparent_meteorite/chrome-extension-permissions-audit

FAQ

How do I run Chrome Extension Permissions Audit: Web Store Data?

Open it on Apify, fill in the input form, and press Start. You can also call it from the Apify API, a schedule, or an AI agent via MCP. Results land in a dataset you can download as JSON, CSV or Excel.

How is it billed?

Pay-per-event on Apify: you are charged only for the events listed in the price table above, plus nothing else from this listing. There is no subscription.

Where does the data come from?

Only publicly available sources. The Actor does not log in to any account or bypass access controls.

Can I use it from an AI assistant?

Yes. Add the MCP URL shown above to any MCP-capable client (Claude, Cursor, VS Code and others) and the Actor becomes a callable tool.