deepbom 1.97.0 → 1.97.3
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 +13 -6
- package/bin/deepbom.mjs +4 -4
- package/package.json +4 -2
- package/pkg/release-manifest.json +2 -2
- package/skills/deepbom/SKILL.md +15 -15
- package/skills/deepbom/scripts/verify-deepbom.mjs +1 -1
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "deepbom",
|
|
3
|
-
"version": "1.97.
|
|
3
|
+
"version": "1.97.3",
|
|
4
4
|
"mcpName": "io.github.JunHwan-Kwon/deepbom",
|
|
5
5
|
"description": "Local multi-format deployment-artifact analysis for on-device AI models",
|
|
6
6
|
"type": "module",
|
|
@@ -45,6 +45,8 @@
|
|
|
45
45
|
"sarif",
|
|
46
46
|
"static-analysis",
|
|
47
47
|
"agent-skills",
|
|
48
|
-
"model-context-protocol"
|
|
48
|
+
"model-context-protocol",
|
|
49
|
+
"mcp",
|
|
50
|
+
"chatgpt"
|
|
49
51
|
]
|
|
50
52
|
}
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"schema": "deepbom.npm_release.v1",
|
|
3
|
-
"version": "1.97.
|
|
3
|
+
"version": "1.97.3",
|
|
4
4
|
"source": {
|
|
5
|
-
"git_commit": "
|
|
5
|
+
"git_commit": "307cd74253fad40892828040abac2280ba3adfe0",
|
|
6
6
|
"git_state": "clean",
|
|
7
7
|
"distribution": "public_channel"
|
|
8
8
|
},
|
package/skills/deepbom/SKILL.md
CHANGED
|
@@ -12,7 +12,7 @@ Run DEEPBOM locally. Never upload artifact bytes or invent a hosted DEEPBOM endp
|
|
|
12
12
|
Use the release pinned by this skill:
|
|
13
13
|
|
|
14
14
|
```bash
|
|
15
|
-
npx -y deepbom@1.97.
|
|
15
|
+
npx -y deepbom@1.97.3 capabilities --format agent-json
|
|
16
16
|
```
|
|
17
17
|
|
|
18
18
|
Treat that machine document as authoritative for commands, supported inputs, scan modes, targets, outputs, and exit codes. Read `references/capability-selection.md` when deciding whether the task belongs to DEEPBOM.
|
|
@@ -22,15 +22,15 @@ Treat that machine document as authoritative for commands, supported inputs, sca
|
|
|
22
22
|
Start with the bounded human result:
|
|
23
23
|
|
|
24
24
|
```bash
|
|
25
|
-
npx -y deepbom@1.97.
|
|
25
|
+
npx -y deepbom@1.97.3 audit "./model.onnx" --summary
|
|
26
26
|
```
|
|
27
27
|
|
|
28
28
|
Then request only the evidence needed by the question:
|
|
29
29
|
|
|
30
30
|
```bash
|
|
31
|
-
npx -y deepbom@1.97.
|
|
32
|
-
npx -y deepbom@1.97.
|
|
33
|
-
npx -y deepbom@1.97.
|
|
31
|
+
npx -y deepbom@1.97.3 audit "./model.onnx" --section quantization --json
|
|
32
|
+
npx -y deepbom@1.97.3 audit "./model.onnx" --pointer /mac_assessment --json
|
|
33
|
+
npx -y deepbom@1.97.3 audit "./model.onnx" --output-format envelope
|
|
34
34
|
```
|
|
35
35
|
|
|
36
36
|
For a large GGUF or SafeTensors artifact, use `--scan structure` for inventory questions. Use `integrity` or `full` only when payload evidence is necessary.
|
|
@@ -38,15 +38,15 @@ For a large GGUF or SafeTensors artifact, use `--scan structure` for inventory q
|
|
|
38
38
|
For a concise GGUF tensor table without nested numerical-integrity ledgers, use the bounded projection (it defaults to a structure scan):
|
|
39
39
|
|
|
40
40
|
```bash
|
|
41
|
-
npx -y deepbom@1.97.
|
|
42
|
-
npx -y deepbom@1.97.
|
|
43
|
-
npx -y deepbom@1.97.
|
|
41
|
+
npx -y deepbom@1.97.3 gguf "./model.gguf" --tensors
|
|
42
|
+
npx -y deepbom@1.97.3 gguf "./model.gguf" --tensors --compact
|
|
43
|
+
npx -y deepbom@1.97.3 gguf "./model.gguf" --tensors --compact --tensor-offset 100 --tensor-limit 100
|
|
44
44
|
```
|
|
45
45
|
|
|
46
46
|
Before relying on a newly fetched package, run:
|
|
47
47
|
|
|
48
48
|
```bash
|
|
49
|
-
npx -y deepbom@1.97.
|
|
49
|
+
npx -y deepbom@1.97.3 self-test --compact
|
|
50
50
|
```
|
|
51
51
|
|
|
52
52
|
## Interpret the result
|
|
@@ -68,12 +68,12 @@ Never infer actual accelerator assignment, latency, energy, thermal behavior, ta
|
|
|
68
68
|
## Compare or explain
|
|
69
69
|
|
|
70
70
|
```bash
|
|
71
|
-
npx -y deepbom@1.97.
|
|
72
|
-
npx -y deepbom@1.97.
|
|
73
|
-
npx -y deepbom@1.97.
|
|
74
|
-
npx -y deepbom@1.97.
|
|
75
|
-
npx -y deepbom@1.97.
|
|
76
|
-
npx -y deepbom@1.97.
|
|
71
|
+
npx -y deepbom@1.97.3 diff "./baseline.onnx" "./candidate.onnx" --summary
|
|
72
|
+
npx -y deepbom@1.97.3 diff "./baseline.gguf" "./candidate.gguf" --tensors --render markdown
|
|
73
|
+
npx -y deepbom@1.97.3 verify "./model.onnx" --bom "./supplied.cdx.json" --render markdown
|
|
74
|
+
npx -y deepbom@1.97.3 contract capture "./model.onnx" -o "./baseline.interface-contract.json"
|
|
75
|
+
npx -y deepbom@1.97.3 explain-rule <rule-id> --json
|
|
76
|
+
npx -y deepbom@1.97.3 graph "./model.onnx" --view structure --format svg -o graph.svg
|
|
77
77
|
```
|
|
78
78
|
|
|
79
79
|
Use matching serialized deployment formats for diff. Treat `verify --bom` as a reconciliation of the selected component with artifact-observable facts, not a complete BOM or compliance verdict. An automatically captured contract is an artifact-derived baseline until it is separately reviewed and approved. Do not deserialize `.pth`, `.pt`, or `.h5`; bind a conversion receipt to the deployed artifact instead.
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
import { spawnSync } from "node:child_process";
|
|
4
4
|
|
|
5
|
-
const VERSION = "1.97.
|
|
5
|
+
const VERSION = "1.97.3";
|
|
6
6
|
const executable = process.platform === "win32" ? process.env.ComSpec || "cmd.exe" : "npx";
|
|
7
7
|
const args = process.platform === "win32"
|
|
8
8
|
? ["/d", "/s", "/c", "npx.cmd", "-y", `deepbom@${VERSION}`, "self-test", "--compact"]
|