registry / @ngockhoale/ukit / 3.4.34
@ngockhoale/ukit@3.4.34
Install/update an index-first AI workspace for Claude Code, OpenAI Codex and omp (Oh My Pi).
AI Security Review
scanned 11d ago · by lpm-firewall-aiInspected source supports ordinary CLI setup and maintenance behavior, and the package has no npm install hook. Scanner hints did not establish malicious behavior.
Static reason
No blocking static signals were detected.
Trigger
The CLI is run by a user; the watchdog runs when invoked as a configured hook.
Impact
No confirmed unauthorized credential access, data transfer, or agent control change was established.
Mechanism
Inspected code manages project configuration and hook behavior, and the package manifest defines no install lifecycle hook.
AI rationale
Inspected source supports ordinary CLI setup and maintenance behavior, and the package has no npm install hook. Scanner hints did not establish malicious behavior.
Decision evidence
public snapshotAI called this Clean at 86.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI and has no install lifecycle hook; its runtime dependency is YAML.
- The benchmark and performance files create fixtures and measure hooks or telemetry; the Codex probe inventories a workspace surface.
- Core setup code protects agent paths, anchors generated ignore entries, and preserves user gateway settings.
- Hook repair targets Claude settings, while uninstall limits cleanup to named project paths.
- The shipped watchdog delegates hook decisions; the audit script reports decision coverage.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemShell
HighEntropyStringsUrlStrings
Source & flagged code
6 flagged · loading sourcescripts/bench/runGold.mjsView file
121const rootDir = projectRoot ?? REPO_ROOT;
L122: const { compileContext } = await import(path.join(REPO_ROOT, 'src/core/codeintel/compiler.js'));
L123: const { routeTask } = await import(path.join(REPO_ROOT, 'src/core/codeintel/router.js'));
Medium
Dynamic Require
Package source references dynamic require/import behavior.
scripts/bench/runGold.mjsView on unpkg · L121scripts/release/verify-release.mjsView file
1import { spawn } from 'node:child_process';
L2: import { readFileSync, writeFileSync, unlinkSync, existsSync } from 'node:fs';
...
L6:
L7: const rootDir = process.cwd();
L8: const npmCacheDir = path.join(os.tmpdir(), 'ukit-npm-cache');
...
L14: // UKIT_VERIFY_STEP_TIMEOUT_MS overrides the step budget for tests.
L15: const STEP_TIMEOUT_MS = Number(process.env.UKIT_VERIFY_STEP_TIMEOUT_MS) || 10 * 60 * 1000; // 10 min
L16: const REGISTRY_TIMEOUT_MS = Number(process.env.UKIT_VERIFY_REGISTRY_TIMEOUT_MS) || 60 * 1000; // 1 min
...
L18: // Opt-in post-publish registry-parity check (Release Policy invariant: npm and git always hold
L19: // the same latest version). Only meaningful AFTER `npm publish` — before publish the registry is
L20: // behind by definition — so it is gated behind --post-
Low
Weak Crypto
Package source references weak cryptographic algorithms.
Findings
2 High4 Medium6 Low
HighPayload In Excluded Dirtemplate_project/.claude/hooks/task-watchdog.sh
HighSemantic Analysis Limitedscripts/audit/decision-coverage.mjs#virtual:normalized:round1
MediumDynamic Requirescripts/bench/runGold.mjs
MediumEnvironment Vars
MediumShips Build Helpertemplate_project/.claude/hooks/task-watchdog.sh
MediumStructural Risk Force Deep Review
LowScripts Present
LowWeak Cryptoscripts/release/verify-release.mjs
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @ngockhoale/ukit@3.4.34.
See all versions of @ngockhoale/ukit for other recorded verdicts.
- Review the evidence and your use of @ngockhoale/ukit@3.4.34 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.