registry / @withfudge/design / 2.0.6
@withfudge/design@2.0.6
Installer and agent guidance for the hosted Fudge design-corpus MCP server.
AI Security Review
scanned 17d ago · by lpm-firewall-aiStatic inspection found no install lifecycle hook or concrete attack behavior. The flagged process and network operations are tied to explicit user-invoked CLI features and package session or workspace setup.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the login or workspace CLI command.
Impact
No unconsented credential transfer, automatic install-time behavior, or other attack impact was identified.
Mechanism
Login uses a browser-based code exchange; workspace commands validate the registry response before writing configuration or invoking npm.
AI rationale
Static inspection found no install lifecycle hook or concrete attack behavior. The flagged process and network operations are tied to explicit user-invoked CLI features and package session or workspace setup.
Evidence
package.jsondist/cli.jsdist/ops/auth.jsdist/ops/login.jsdist/ops/workspace.js
Network endpoints1
api.withfudge.com
Decision evidence
public snapshotAI called this Clean at 95.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 scripts are build, prepack, test, and typecheck.
- The authentication process calls use fixed macOS Keychain commands to read, store, and delete the package session.
- The CLI starts browser login only for the explicit login command; the login flow exchanges a one-time code with the configured Fudge API and stores the returned session.
- Workspace connection and package installation run only after an explicit workspace add or connect command; registry responses are checked against the chosen API origin.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
4 flaggeddist/ops/auth.jsView file
4import { join } from "node:path";
L5: import { execFile } from "node:child_process";
L6: import { promisify } from "node:util";
High
dist/ops/login.jsView file
107const args = process.platform === "win32" ? ["/c", "start", "", url] : [url];
L108: const child = spawn(command, args, { stdio: "ignore", detached: true });
L109: child.unref();
...
L118: function apiBase(value) {
L119: return (value || process.env.FUDGE_API_BASE || "https://api.withfudge.com").replace(/\/+$/, "");
L120: }
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/ops/login.jsView on unpkg · L1071import { createHash, randomBytes } from "node:crypto";
L2: import { spawn } from "node:child_process";
L3: import { createServer } from "node:http";
L4: import { writeSession } from "./auth.js";
...
L6: export async function browserLoopbackLogin(options = {}) {
L7: const state = randomBase64url(24);
L8: const codeVerifier = randomBase64url(48);
...
L39: headers: { "content-type": "application/json" },
L40: body: JSON.stringify({ code, code_verifier: codeVerifier }),
L41: });
...
L101: function openInBrowser(url) {
L102: const command = process.platform === "darwin"
Findings
4 High3 Medium5 Low
HighChild Processdist/ops/auth.js
HighSame File Env Network Executiondist/ops/login.js
HighSandbox Evasion Gated Capabilitydist/ops/login.js
HighRuntime Package Installdist/ops/workspace.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @withfudge/design@2.0.6.
See all versions of @withfudge/design for other recorded verdicts.
- Review the evidence and your use of @withfudge/design@2.0.6 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.