Electron Release Inspector

    1

    Compare two builds of your own Electron app (app.asar or extracted app directory, optionally the packaged executables) before shipping, and turn the static release-diff report into a prioritized revie

    $29

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    About this skill

    Electron Release Inspector

    Review what changed between two builds of an Electron application the user owns or is authorized to analyze, using the electron-release-inspector CLI, and produce a prioritized, evidence-backed release review.

    Scope and rules

    • Only analyze builds the user supplied or confirms they are authorized to inspect (their own app, their employer's app, or an explicitly permitted engagement). If authorization is unclear, ask before running anything.
    • The CLI is static: it never launches, attaches to, or debugs the target. Do not run the target app yourself either.
    • Never try to recover, print, or reuse a detected secret. Report findings only by the masked fingerprint, file, and line the tool provides, and recommend rotation.
    • Do not overclaim. "Not determined" means the analysis could not resolve it, not that it is safe. A diff report is not a full security audit.

    1. Collect inputs

    Ask for, or locate in the user's build output:

    InputTypical locationRequired
    Old build (--left)release/<old>/win-unpacked/resources/app.asar, .../Contents/Resources/app.asar, or an extracted app/ directoryyes
    New build (--right)same layout for the candidate releaseyes
    Old/new executable (--left-exe / --right-exe)MyApp.exe, MyApp.app/Contents/MacOS/MyApp, Linux binaryrecommended (enables fuse checks)

    Both sides should be the same platform and packaging layout, otherwise most differences are noise.

    2. Run

    Requires Node ^22.19.0 || ^24.11.0 || >=26 and network access on first run (npx fetches the pinned packages).

    npx -y electron-release-inspector@0.2.0 \
      --left <old app.asar|dir> --right <new app.asar|dir> \
      --left-exe <old exe> --right-exe <new exe> \
      --out eri-report/report.html
    

    Outputs: report.html (human report), report.json (read this one), and report-evidence/ (raw analysis JSON for traceability).

    For large apps prefer --scope focused first: it restricts graph analysis to application files outside node_modules/ (REA --source-path, keeps Evidence small) while file/package diffs still cover the whole inventory. If that is still too heavy — or evidence grows past a few hundred MB — rerun with --no-rea. That mode still compares files, shipped packages, declared dependencies, secrets, and fuses, but does not analyze webPreferences, IPC, contextBridge, or endpoints; say so in your review. If JSON parsing fails on a large app, retry with NODE_OPTIONS=--max-old-space-size=8192.

    3. Read report.json

    Key fields:

    • mode: "rea" (full), "rea-focused" (app files only, no node_modules graph), or "no-rea" (limited, see above).
    • findings[]: each has id, severity (high / medium / info), category, title, rationale, confidence, evidence (locations, node_id, evidence_links), and optional fuse / domain / sender_validation_candidates.
      • category: "change" — introduced or altered by this release. This is the core of the review.
      • category: "posture" — current state of the shipped build (mostly fuses). The rationale says when it is unchanged from the previous version; present those as pre-existing, not as regressions.
      • category: "inventory" — added/removed/changed files and modules. Context only.
    • deps: declared dependency changes, lockfil

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 26 days ago

    Software
    fetchesNode.jselectron-release-inspector

    Permissions

    Terminal / Shell
    Listed26 days ago

    What's inside

    Frequently Asked Questions

    Compare two builds of your own Electron app (app.asar or extracted app directory, optionally the packaged executables) before shipping, and turn the static release-diff report into a prioritized revie

    This skill uses the open SKILL.md standard. Use it through an MCP-compatible agent connected to Agensi, and check the compatibility information on this page for confirmed agents and required capabilities.

    Connect your AI agent to Agensi through MCP, then ask it to use electron-release-inspector on your task. Your agent loads the latest approved version each time. Paid skills require a purchase or active subscription. Skill files are not available for download; your licence does not allow you to save, copy or export any part of a skill.

    New in Security