glasspane-harness 0.14.14 → 0.14.15

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -157,7 +157,7 @@ npm install -g glasspane-harness
157
157
  bun add -g glasspane-harness
158
158
 
159
159
  # or one-click (npm first, GitHub release asset as fallback)
160
- curl -fsSL https://raw.githubusercontent.com/jingzhao-l/glasspane-harness/v0.14.14/scripts/install.sh | bash
160
+ curl -fsSL https://raw.githubusercontent.com/jingzhao-l/glasspane-harness/v0.14.15/scripts/install.sh | bash
161
161
  ```
162
162
 
163
163
  Two commands are installed: **`glasspane-harness`** and the short alias **`gp-harness`**. npm and
package/README.zh-CN.md CHANGED
@@ -135,7 +135,7 @@ Azure、OpenRouter 等等全在——几百个模型——每一个都用**你
135
135
  ```bash
136
136
  npm install -g glasspane-harness # 推荐
137
137
  bun add -g glasspane-harness
138
- curl -fsSL https://raw.githubusercontent.com/jingzhao-l/glasspane-harness/v0.14.14/scripts/install.sh | bash
138
+ curl -fsSL https://raw.githubusercontent.com/jingzhao-l/glasspane-harness/v0.14.15/scripts/install.sh | bash
139
139
  ```
140
140
 
141
141
  会装出两个命令:**`glasspane-harness`** 与短别名 **`gp-harness`**。npm 与 bun 从 wrapper 的
package/package.json CHANGED
@@ -25,7 +25,7 @@
25
25
  "scripts": {
26
26
  "postinstall": "node ./postinstall.mjs"
27
27
  },
28
- "version": "0.14.14",
28
+ "version": "0.14.15",
29
29
  "license": "MIT",
30
30
  "os": [
31
31
  "darwin"
@@ -44,7 +44,7 @@
44
44
  },
45
45
  "sideEffects": false,
46
46
  "optionalDependencies": {
47
- "glasspane-harness-darwin-arm64": "0.14.14",
48
- "glasspane-harness-darwin-x64": "0.14.14"
47
+ "glasspane-harness-darwin-arm64": "0.14.15",
48
+ "glasspane-harness-darwin-x64": "0.14.15"
49
49
  }
50
50
  }
package/postinstall.mjs CHANGED
@@ -330,11 +330,11 @@ function installPackage(name) {
330
330
  //
331
331
  // This branch then goes one step further than "name the registry": it downloads the
332
332
  // tarball with `npm pack`, re-computes its sha512, and refuses it unless that hash equals
333
- // the `dist.integrity` the registry itself advertises. npm's own integrity check happens
334
- // against the registry's self-attested metadata during unpack — a mirror that serves a
335
- // tampered tarball can attest it with matching metadata. Comparing the bytes WE downloaded
336
- // against the registry's own claim closes that: `npm install <tarball>` below consumes
337
- // exactly the bytes we verified, never a re-fetch.
333
+ // the `dist.integrity` the registry itself advertises. This closes a tarball whose bytes
334
+ // diverge from the integrity the registry advertises for that version — storage/mirror
335
+ // corruption serving one blob under another version's correct metadata. It does NOT close
336
+ // a MITM that also rewrites the `npm view dist.integrity` answer: both halves come from the
337
+ // same pinned origin over one channel, and npm tarballs carry no client-enforced signature.
338
338
  const integrityProbe = childProcess.spawnSync(
339
339
  "npm",
340
340
  ["view", `${name}@${version}`, "dist.integrity", "--registry", REGISTRY],