registry / @oked/claude-code / 0.6.2
@oked/claude-code@0.6.2
OKed for Claude Code - zero-code human approval for sensitive actions
AI Security Review
scanned 28d ago · by lpm-firewall-aiSource inspection shows project configuration and device pairing are activated by the explicit init command; package.json has no install-time hook. The scanner's process and network signals are consistent with this CLI behavior, and no concrete attack was established.
Static reason
One or more suspicious static signals were detected.
Trigger
The user runs the oked init command.
Impact
This enables the package's stated approval workflow; inspected behavior does not establish credential theft or unconsented installation-time mutation.
Mechanism
The CLI updates the project's .claude/settings.json with the OKed hook and pairs with the configured OKed backend.
AI rationale
Source inspection shows project configuration and device pairing are activated by the explicit init command; package.json has no install-time hook. The scanner's process and network signals are consistent with this CLI behavior, and no concrete attack was established.
Evidence
.claude/settings.json
Network endpoints1
api.oked.ai
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes CLI commands and has no install lifecycle hook; its listed scripts are build and prepublishOnly tasks.
- The indicated settings path is the current project's .claude/settings.json, and init adds or updates the OKed hook there.
- Pairing sends a device code request to the configured OKed backend, defaulting to api.oked.ai.
- Hook installation runs through the explicit init command.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
UrlStrings
Source & flagged code
6 flaggeddist/cli.jsView file
4import { join, dirname } from "path";
L5: import { spawn } from "child_process";
L6: import { createInterface } from "readline";
High
4import { join, dirname } from "path";
L5: import { spawn } from "child_process";
L6: import { createInterface } from "readline";
...
L10: import { OKED_RECEIPTS_LOG, verifyReceiptsFile } from "./receipts.js";
L11: const DEFAULT_BACKEND_URL = process.env.OKED_BACKEND_URL || "https://api.oked.ai";
L12: function getSettingsPath() {
High
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/cli.jsView on unpkg · L44import { join, dirname } from "path";
L5: import { spawn } from "child_process";
L6: import { createInterface } from "readline";
...
L10: import { OKED_RECEIPTS_LOG, verifyReceiptsFile } from "./receipts.js";
L11: const DEFAULT_BACKEND_URL = process.env.OKED_BACKEND_URL || "https://api.oked.ai";
L12: function getSettingsPath() {
L13: return join(process.cwd(), ".claude", "settings.json");
L14: }
...
L18: try {
L19: return JSON.parse(readFileSync(path, "utf-8"));
L20: }
...
L45: function openBrowser(url) {
Findings
3 High2 Medium7 Low
HighChild Processdist/cli.js
HighSame File Env Network Executiondist/cli.js
HighSandbox Evasion Gated Capabilitydist/cli.js
MediumNetwork
MediumEnvironment Vars
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/cli.js
LowAi Review Evidencedist/cli.js
Affected versions and remediation
This report applies to @oked/claude-code@0.6.2.
See all versions of @oked/claude-code for other recorded verdicts.
- Review the evidence and your use of @oked/claude-code@0.6.2 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.