AI Security Review
scanned 9d ago · by lpm-firewall-aiNo confirmed malicious attack surface was established. The package is a developer configuration CLI with potentially broad project mutations only after explicit command invocation.
Decision evidence
public snapshot- src/index.ts exposes user-invoked commands that run bunx tools, husky, and killPort shell commands
- src/manage-overrides.ts can rewrite the consumer package.json overrides and run bun install when config prepare is invoked
- src/vscode-config.ts writes .vscode/extensions.json and .vscode/settings.json on config prepare
- src/patch-vanilla-extract.ts rewrites installed @vanilla-extract files under node_modules on config prepare
- package.json has no install/postinstall/prepare lifecycle hook; only prepublishOnly for publisher-side use
- bin entry src/index.ts requires explicit CLI invocation and prints help by default
- No fetch/http/curl/wget or package-specific exfiltration endpoints found
- No credential harvesting, home-directory agent config writes, MCP/Claude/Codex/Cursor control-surface mutation, or persistence found
- Child process usage is package-aligned developer tooling: tsc, oxfmt, oxlint, husky, bun install, and port cleanup
Source & flagged code
4 flagged · loading sourcePackage source references child process execution.
src/vscode-config.tsView on unpkg · L1Package source references dynamic require/import behavior.
src/link-packages.tsView on unpkg · L21Package source invokes a package manager install command at runtime.
src/manage-overrides.tsView on unpkg · L60This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
src/index.tsView on unpkg