Chrome Extension Permissions Scraper

This Actor extracts public Chrome Web Store permission and host-access declarations while also returning a rich extension listing record. One normal dataset row represents one extension and includes the full public Overview, developer/contact data, listing metrics, privacy disclosures, technical metadata, media, version information, and the structured permission profile.

Scope and access boundary

Only public Chrome Web Store pages are in scope. The Actor does not log in, solve CAPTCHAs, access private APIs, or infer permissions not present in the listing. If a page is blocked or unavailable, the run summary and logs report the issue without adding an invalid extension record.

Inputs

Use extensionId or extensionIds for known extensions, or provide public Chrome Web Store detail, search, or category URLs with startUrls, sourceUrls, or urls. For discovery, use queries, query, or searchQuery with optional category paths. page selects the starting page for search/category sources, and maxPages sets the page limit per source; ID lookups start from the first search page. maxItems, maxRequests, and maxDetailRequests bound records and public pages collected. proxyConfiguration can route permitted public requests through Apify Proxy.

Output

Each dataset row represents an extension and can include its canonical identity and URLs; overview, category, and publisher details; ratings and user counts; version and update information; required and optional API or host permissions; content-script access; privacy disclosures; support links; related extensions; features, media, and version history. permissionCategory groups permission names into site access, browsing activity, storage, clipboard, device/system, or browser-feature categories.

Required permissions, optional permissions, host permissions, and optional host permissions remain separate. permissionDataAvailable, hasAllSitesAccess, and broadHostAccess preserve unknown source coverage instead of interpreting an absent declaration as a negative permission.

All-site access includes <all_urls>, *://*/*, http://*/*, and https://*/*. Exact schemes remain in hostPermissionDetails; an HTTP-only wildcard is not silently described as granting HTTPS access. Wildcard subdomains of one named domain are broad access, but not all-site access.

You can download the dataset in formats such as JSON, HTML, CSV, or Excel. The run summary is available alongside it in the Output tab.

Example public listing

The AdBlock Chrome Web Store listing is an example public detail page. Permission data is included only when the public listing exposes it; the Actor does not infer missing permissions or access hidden APIs.