@akasecurity/ai-tc-claude-code 0.9.6 → 0.9.7

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.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "aka",
3
- "version": "0.9.6",
3
+ "version": "0.9.7",
4
4
  "description": "AI Traffic Control — inspect and govern AI prompts in Claude Code. Detection runs locally; events are recorded to a local SQLite store on your machine.",
5
5
  "homepage": "https://github.com/akasecurity/ai-tc",
6
6
  "author": { "name": "AKA Security" }
package/commands/setup.md CHANGED
@@ -892,26 +892,3 @@ declined, or a failed install you already reported — end with one warm close:
892
892
 
893
893
  Before you finish, confirm every AKA_SHOW region on the path you took was
894
894
  relayed to the user. If you summarized one instead of pasting it, paste it now.
895
-
896
- ## Known limitations
897
-
898
- Be honest about every one of these if the user asks why something wasn't caught
899
- — never imply coverage this plugin does not have.
900
-
901
- **The model-judge step in step 3 cannot run on native Windows.** The judge
902
- spawns the `claude` CLI through a shell-free `execFileSync`, and an
903
- npm-installed CLI is a `.cmd` shim on Windows, which Node has refused to spawn
904
- without a shell since the CVE-2024-27980 fix. So a user who grants model-judge
905
- consent gets a spawn failure at that step rather than a rated set of findings,
906
- and the step exits non-zero instead of completing. Everything before it is
907
- unaffected — the posture check, the consent-gated historical read, and the local
908
- ruleset scan all run, and every finding is still detected and redacted locally.
909
- What is unavailable is only the model pass that rates false positives and
910
- severity.
911
-
912
- Say this plainly if a Windows user asks why setup stopped there, and do not
913
- offer to retry it: the fix is a code change, tracked separately. Two things
914
- worth getting right if it comes up — running under WSL2 is Linux rather than
915
- Windows and is not affected, and declining model-judge consent in step 1 is not
916
- a workaround so much as the other supported path, since the local scan is what
917
- produces the findings in the first place.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@akasecurity/ai-tc-claude-code",
3
- "version": "0.9.6",
3
+ "version": "0.9.7",
4
4
  "description": "AI Traffic Control — inspect and govern AI prompts in Claude Code",
5
5
  "license": "Apache-2.0",
6
6
  "type": "module",
@@ -22,18 +22,19 @@
22
22
  },
23
23
  "devDependencies": {
24
24
  "@types/node": "^24.13.3",
25
- "eslint": "^9.0.0",
25
+ "@vitest/coverage-v8": "^4.1.10",
26
+ "eslint": "^9.39.5",
26
27
  "tsup": "^8.0.0",
27
28
  "typescript": "^5.8.0",
28
29
  "vitest": "^4.1.10",
29
30
  "zod": "^4.0.0",
30
31
  "@akasecurity/eslint-config": "0.8.0",
32
+ "@akasecurity/plugin-runtime": "0.8.0",
31
33
  "@akasecurity/persistence": "0.8.0",
32
34
  "@akasecurity/plugin-sdk": "0.8.0",
33
- "@akasecurity/scanner": "0.8.0",
34
35
  "@akasecurity/schema": "0.8.0",
35
- "@akasecurity/plugin-runtime": "0.8.0",
36
- "@akasecurity/setup-wizard": "0.8.0"
36
+ "@akasecurity/setup-wizard": "0.8.0",
37
+ "@akasecurity/scanner": "0.8.0"
37
38
  },
38
39
  "scripts": {
39
40
  "build": "tsup",