zcode-agent-kit@0.2.1
Local ZCode provider kit: run GLM-5.3 / GLM-5.3-Flash from your own ZCode Desktop account inside your own agent harnesses (OMP, pi, Claude Code, Codex, OpenCode, Cline, Kilo Code, Aider, Continue, Goose).
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe postinstall hook automatically runs setup, and setup applies detected harness integrations, including a write to the OMP agent configuration. This confirms unconsented install-time mutation of a foreign agent control surface.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package through npm triggers postinstall.
Impact
Agent configuration can be changed without a separate user-invoked setup command.
Mechanism
The lifecycle invokes setup, which defaults to detected harnesses and applies their adapters; the OMP adapter edits ~/.omp/agent/models.yml when present.
Policy narrative
During npm installation, postinstall invokes setup. Setup defaults to detected harnesses and applies their adapters; the OMP adapter writes a provider entry into the user's agent models configuration. This is an unconsented install-time change to an AI-agent control surface.
AI rationale
The postinstall hook automatically runs setup, and setup applies detected harness integrations, including a write to the OMP agent configuration. This confirms unconsented install-time mutation of a foreign agent control surface.
Evidence
package.jsonsetup.mjscli/zcode-kit.mjscli/adapters/omp.mjs
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 98.0% confidence with low false-positive risk.
Evidence for policy risk
- package.json runs setup.mjs from postinstall.
- setup.mjs forwards postinstall arguments to the setup command without requiring an explicit setup action.
- Setup defaults to auto and selects detected harness adapters.
- The OMP adapter modifies the user's agent models configuration during setup.
Evidence against
- The OMP adapter checks for an existing models file and refuses to overwrite a hand-written provider entry.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
11 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node setup.mjs --postinstall-hint
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node setup.mjs --postinstall-hint
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgsetup.mjsView file
11// duplicated setup logic). Legacy flags map as: --only=<list> → --harness=<list>.
L12: import { spawnSync } from "node:child_process";
L13: import { join, dirname } from "node:path";
High
Findings
7 High5 Medium7 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processsetup.mjs
HighShellproxy/zcode-proxy-manager.mjs
HighSame File Env Network Executioncli/zcode-kit.mjs
HighSandbox Evasion Gated Capabilitycli/adapters/aider.mjs
HighRuntime Package Installproxy/zcode-proxy-manager.mjs
HighSemantic Analysis Limitedcli/adapters/omp.mjs#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperbin/zcode-aider.cmd
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
Affected versions and remediation
This report applies to zcode-agent-kit@0.2.1.
See all versions of zcode-agent-kit for other recorded verdicts.
- Avoid installing zcode-agent-kit@0.2.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.