maximilianfeix/hexvero

概要

The interfaces pages can call, window settings and network hosts that changed between two builds, with the file and line on both sides, what could not be established, and a policy gate for CI. Locally, without executing the target. The local web UI comparing two builds of the example app in examples/. Real output. 25 seconds, real output of the commands below: two releases, one new member pages can call with both places it was read from, a channel that is unknown rather than removed, and the policy failing with exit 3 · mp4 · recorded with docs/demo/release-gate.tape Node.js 22.12 or newer is all it needs. demo copies two builds of a small example Electron app and an example policy into ./hexvero-demo and shows what changed between them, with the place each change was read from: 1.5.0 adds checkUpdate, a member pages can call, whose handler at main.js:30 fetches a new host. shell:open exists only in 1.4.0, but 1.5.

README

以下は原文 README の抜粋です。原文を見る。

npx hexvero demo

What changed between notesdesk-1.4.0.asar and notesdesk-1.5.0.asar
  Two builds of a small example Electron app, read statically. Nothing was executed.

  interfaces (2)
    + preload.js::notesdesk::checkUpdate  @ b: preload.js:9, handler main.js:30 · link direct
    - preload.js::notesdesk::openInShell  @ a: preload.js:9, handler main.js:30 · link direct
  …
  ipcChannels (2)
    + update:check  @ b: receiver main.js:30, sender preload.js:9
    ? shell:open  @ a: receiver main.js:30, sender preload.js:9
        the other side has values there that could not be resolved
  windows (1)
    ~ main.js::win  @ b: main.js:8
        nodeIntegration: true → false, nodeIntegrationInEffect: "on" → "off", sandbox: false → true
  …

インストール