# Chrome Extension Permission Diff Monitor (`bakos_bence/chrome-extension-permission-monitor`) Actor

Download Chrome Web Store extension CRX packages, parse manifest permissions, and emit baseline snapshots or permission/version diffs on scheduled runs. Unofficial; not affiliated with Google or extension authors.

- **URL**: https://apify.com/bakos\_bence/chrome-extension-permission-monitor.md
- **Developed by:** [Bakos Bence](https://apify.com/bakos_bence) (community)
- **Categories:** Developer tools, Automation, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.25 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### What does Chrome Extension Permission Diff Monitor do?

**Download Chrome Web Store extension packages**, parse `manifest.json`, and emit **permission baseline snapshots** or **diff events** when permissions or version change between runs. Uses Google's public CRX update endpoint (with open-source release fallback when Google returns HTTP 204). **No login, no API keys.**

**Unofficial.** This Actor is **not affiliated with, endorsed by, or maintained by** Google, the Chrome Web Store, or any extension author.

**Dashboards:** connect **Power BI**, **Tableau**, **Looker Studio**, or **Qlik** to the dataset API — see *Export to Power BI, Tableau, Looker Studio & Qlik* near the end. **AI agents:** paste this Actor's Store page URL into an Apify-capable agent (MCP / Claude / Cursor with Apify), create an Apify account and API token once, and the agent can run the Actor and wire up the output.

#### Why use this extension permission monitor?

- 🔐 Track `permissions`, `host_permissions`, and version over time
- 📦 Direct CRX download — lightweight HTTP, no browser
- 🔄 Baseline + scheduled diff mode with KV store persistence
- 🛡️ Fail loud when an extension cannot be fetched

#### How to monitor extension permissions

1. Open this Actor in [Apify Console](https://console.apify.com/).
2. Click **Start** on the prefilled uBlock Origin id (`maxItems` 5) to emit a baseline row.
3. Schedule later runs with `monitorMode: true` to receive only permission/version diffs.
4. Export the dataset or pull via API.

```json
{
  "extensionIds": ["cjpalhdlnbpafiamejdnhcphjbkeiagm"],
  "maxItems": 5,
  "emitBaseline": true,
  "monitorMode": false,
  "proxyType": "none"
}
```

#### How much does it cost?

**Pay per event (PPE):** Actor start + each dataset **result** row. On Free, results are about **$0.49 / 1,000**; paid plans are lower (see the Pricing tab).

#### Input

| Field | Description |
|-------|-------------|
| `extensionIds` | Chrome Web Store extension IDs |
| `maxItems` | Cap on rows emitted |
| `emitBaseline` | Emit full snapshot rows (`changeType: baseline`) |
| `monitorMode` | Emit only diffs when baseline exists |
| `baseline` | Optional baseline map; otherwise loaded from KV `PERMISSION_BASELINE` |
| `proxyType` | Optional proxy |

#### Sample output

```json
{
  "extensionId": "cjpalhdlnbpafiamejdnhcphjbkeiagm",
  "name": "uBlock Origin",
  "version": "1.74.0",
  "permissions": ["alarms", "contextMenus", "privacy", "storage", "tabs", "unlimitedStorage", "webNavigation", "webRequest", "webRequestBlocking"],
  "hostPermissions": ["<all_urls>"],
  "changeType": "baseline",
  "detail": "initial snapshot",
  "scrapedAt": "2026-09-09T10:00:00+00:00",
  "sourceUrl": "https://clients2.google.com/service/update2/crx?..."
}
```

#### FAQ

##### Is this official Google software?

No. It is unofficial and not affiliated with Google or the Chrome Web Store.

##### Why might an extension fail to download?

Some extensions return HTTP 204 from Google's update endpoint. Known open-source extensions (e.g. uBlock Origin) fall back to the author's GitHub release CRX.

##### Can AI agents call this?

Yes — Actor ID `bakos_bence/chrome-extension-permission-monitor` via Apify API or [MCP](https://mcp.apify.com).

##### Something broke?

Open the **Issues** tab on this Actor's page.

#### Related Actors

| Actor | Use together when… |
|-------|-------------------|
| [Domain Typosquat Scanner](https://apify.com/bakos_bence/domain-typosquat-scanner) | Brand / domain risk monitoring alongside extension supply-chain checks |
| [Public Document Finder](https://apify.com/bakos_bence/public-document-finder) | You need regulatory filings alongside security monitoring |

Profile: [bakos\_bence on Apify](https://apify.com/bakos_bence).

#### For AI agents & LLM apps

Paste this Actor's **Apify Store URL** into an agent that can use Apify (MCP, Claude, Cursor, etc.). With an Apify account and API token, the agent can set input, run the Actor, and fetch the dataset.

#### Export to Power BI, Tableau, Looker Studio & Qlik

1. Run the Actor (or open a finished run).
2. Open the **Dataset** → **API** / **Export**.
3. Copy the dataset items URL (JSON or CSV).
4. In your BI tool, add a **web / API** data source with that URL (and your Apify token as a header or query param if required).
5. Refresh on a schedule that matches your extension monitoring cadence.

Permission facts come from public extension manifests — verify critical security decisions against your own review process.

# Actor input Schema

## `extensionIds` (type: `array`):

Chrome Web Store extension IDs (32 lowercase letters a–p). Default is uBlock Origin.

## `maxItems` (type: `integer`):

Cap dataset rows (baseline or diff events). Leave at 5 for a cheap first run.

## `emitBaseline` (type: `boolean`):

When true (default), emit a baseline row per extension with current permissions and version.

## `monitorMode` (type: `boolean`):

When true and a baseline exists, emit only permission/version changes instead of full snapshots.

## `baseline` (type: `object`):

Optional baseline map keyed by extensionId. When omitted, the Actor loads/saves PERMISSION\_BASELINE in key-value store.

## `proxyType` (type: `string`):

Leave on none for Google update endpoints. Enable Apify Proxy only if your IP is blocked.

## `proxyConfiguration` (type: `object`):

Used only when Proxy is Apify Proxy.

## Actor input object example

```json
{
  "extensionIds": [
    "cjpalhdlnbpafiamejdnhcphjbkeiagm"
  ],
  "maxItems": 5,
  "emitBaseline": true,
  "monitorMode": false,
  "baseline": {},
  "proxyType": "none",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

Default dataset items.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "extensionIds": [
        "cjpalhdlnbpafiamejdnhcphjbkeiagm"
    ],
    "maxItems": 5,
    "emitBaseline": true,
    "monitorMode": false,
    "proxyType": "none"
};

// Run the Actor and wait for it to finish
const run = await client.actor("bakos_bence/chrome-extension-permission-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "extensionIds": ["cjpalhdlnbpafiamejdnhcphjbkeiagm"],
    "maxItems": 5,
    "emitBaseline": True,
    "monitorMode": False,
    "proxyType": "none",
}

# Run the Actor and wait for it to finish
run = client.actor("bakos_bence/chrome-extension-permission-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "extensionIds": [
    "cjpalhdlnbpafiamejdnhcphjbkeiagm"
  ],
  "maxItems": 5,
  "emitBaseline": true,
  "monitorMode": false,
  "proxyType": "none"
}' |
apify call bakos_bence/chrome-extension-permission-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bakos_bence/chrome-extension-permission-monitor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/4fAn87cClr3439oGz/builds/DyYGJPUAXybeUEKp5/openapi.json