@holmes-lab/holmes-kit 0.19.4 → 0.19.5
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/CHANGELOG.md +26 -0
- package/dist/.build-id +1 -1
- package/package.json +4 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,32 @@ All notable changes to this project will be documented in this file.
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
7
|
<!-- @implements A-SPEC-209 -->
|
|
8
|
+
## [0.19.5] - 2026-09-11
|
|
9
|
+
|
|
10
|
+
One critical supply-chain advisory removed, by measuring a prediction this project had written down
|
|
11
|
+
and found to be wrong.
|
|
12
|
+
|
|
13
|
+
### Security
|
|
14
|
+
- **`protobufjs` is overridden to 7.x, and the critical advisory is gone** (REQ-601). The arbitrary
|
|
15
|
+
code execution lives in protobufjs's 6.x line, reached three levels down —
|
|
16
|
+
`@xenova/transformers → onnxruntime-web → onnx-proto → protobufjs@6.11.6` — and this project's own
|
|
17
|
+
supply-chain note predicted that overriding it would break `onnx-proto`, which pins 6.x. That
|
|
18
|
+
prediction was **refuted**: the Windows qualification run measured it first (critical 0 / high 3,
|
|
19
|
+
inference intact) and macOS reproduced it with protobufjs as the only variable, verifying import,
|
|
20
|
+
`ModelProto.decode`, and a **real 1024-dimension normalized inference** — the path where
|
|
21
|
+
`onnx-proto` actually decodes a model, which is where a 6→7 incompatibility would surface.
|
|
22
|
+
|
|
23
|
+
| | critical | high | protobufjs |
|
|
24
|
+
|---|---|---|---|
|
|
25
|
+
| 0.19.4 | 1 | 5 | 6.11.6 |
|
|
26
|
+
| **0.19.5** | **0** | **3** | **7.6.6** |
|
|
27
|
+
|
|
28
|
+
A guard reads the **lockfile**, not the manifest: the manifest is the intent and the lock is the
|
|
29
|
+
fact, so asserting the declaration alone would stay green while the override was being ignored —
|
|
30
|
+
and an override that quietly stops applying brings the critical back without a word. The remaining
|
|
31
|
+
three highs (`@xenova/transformers`, `js-yaml`, `sharp`) are untouched and still recorded, with
|
|
32
|
+
their re-evaluation triggers, in `docs/goals/supply-chain-xenova-2026-09.md`.
|
|
33
|
+
|
|
8
34
|
## [0.19.4] - 2026-09-10
|
|
9
35
|
|
|
10
36
|
Three Windows diagnoses that pointed the wrong way, found by running the Windows plan on a real
|
package/dist/.build-id
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
|
|
1
|
+
5efeb5b9-mtx1x7js
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"//": "@implements A-SPEC-209",
|
|
3
3
|
"name": "@holmes-lab/holmes-kit",
|
|
4
|
-
"version": "0.19.
|
|
4
|
+
"version": "0.19.5",
|
|
5
5
|
"description": "Holmes-Kit — deterministic Agentic Software Engineering (ASE) harness with causal traceability (spec chain + D-CPG + RTM + phase guardrail)",
|
|
6
6
|
"main": "dist/holmes/mcp/server.js",
|
|
7
7
|
"types": "dist/holmes/mcp/server.d.ts",
|
|
@@ -91,5 +91,8 @@
|
|
|
91
91
|
"allowScripts": {
|
|
92
92
|
"better-sqlite3@12.11.1": true,
|
|
93
93
|
"sharp@0.32.6": true
|
|
94
|
+
},
|
|
95
|
+
"overrides": {
|
|
96
|
+
"protobufjs": "^7.6.3"
|
|
94
97
|
}
|
|
95
98
|
}
|