registry / @vnejs/monorepo / 0.0.7

@vnejs/monorepo@0.0.7

Monorepo tooling for @vnejs

AI Security Review

scanned 16d ago · by lpm-firewall-ai

No confirmed malicious attack surface is established. The package is monorepo tooling with powerful user-invoked shell operations for build, test, publish, dependency sync, and cleanup.

Static reason

One or more suspicious static signals were detected.

Trigger

Explicit CLI/API calls such as publish, run, run-changed, sync-deps, package, test, or clear

Impact

Can modify project package metadata, publish packages, run workspace scripts, or clean build/dependency artifacts when invoked by the user

Mechanism

user-invoked npm/git/turbo/typescript/vitest shell commands and package metadata edits

Rationale

Static inspection shows suspicious primitives are expected for a monorepo/publish CLI and require explicit user commands; there is no lifecycle execution, hidden exfiltration, persistence, or unconsented control-surface mutation. Shell command construction has some user-controlled arguments, but this is local developer tooling behavior rather than a concrete malicious package attack.

Evidence

package.jsonsrc/cli.jssrc/index.jssrc/publish/index.jssrc/publish/utils.jssrc/workspace/fetch-npm-version.jssrc/run/index.jssrc/run-changed/index.jssrc/clear/index.jssrc/sync-deps/index.jssrc/package/index.jssrc/test/index.jspackage-lock.jsonnode_modules.turbodist

Decision evidence

public snapshot

AI called this Clean at 89.0% confidence as Benign with low false-positive risk.

Evidence for block

src/clear/index.js can remove node_modules, .turbo, dist, and package-lock.json when the clear CLI command is invoked.
src/run/index.js and src/run-changed/index.js execute user-selected npm scripts via shell commands.
src/workspace/fetch-npm-version.js shells out to npm view and npm cache clean for registry/version workflow.

Evidence against

package.json has no install/preinstall/postinstall lifecycle hooks.
src/cli.js exposes explicit monorepo maintenance commands; no code runs merely on import beyond require wiring in src/index.js.
src/publish/index.js only runs npm version/publish from the current package when the publish command is invoked.
No credential harvesting, environment dumping, hidden exfiltration endpoints, persistence, binary loading, or AI-agent control-surface writes found.
File writes are package-aligned version/dependency updates in package.json and package-lock.json.
Destructive clear behavior is an explicit CLI maintenance command, not install-time behavior.

Behavioral surface

Source

ChildProcess

Source & flagged code

2 flagged

src/workspace/fetch-npm-version.jsView file

Lines 1-21javascript

1const { execSync } = require("child_process");

2const { parseExpectVersion, shouldWaitForExpectVersion } = require("./expect-version");

High

Child Process

Package source references child process execution.

src/workspace/fetch-npm-version.jsView on unpkg · L1

4const fetchRaw = (name) => {

5 try {

6 return execSync(`npm view ${JSON.stringify(name)} version`, {

7 encoding: "utf8",

8 stdio: ["ignore", "pipe", "ignore"],

9 }).trim();

10 } catch {

11 return null;

12 }

13};

15const clearNpmCache = () => {

16 execSync("npm cache clean --force", { stdio: "inherit" });

17};

19const sleepSync = (ms) => {

20 execSync(`sleep ${Math.max(1, Math.ceil(ms / 1000))}`, { stdio: "ignore" });

21};

src/publish/utils.jsView file

Lines 7-39javascript

7const readVersion = (pkgDir) => readPackageJson(pkgDir).version;

9const readPackageName = (pkgDir) => readPackageJson(pkgDir).name;

Source & flagged code

2 flagged · loading source

src/workspace/fetch-npm-version.jsView file

1const { execSync } = require("child_process"); L2: const { parseExpectVersion, shouldWaitForExpectVersion } = require("./expect-version");

High

Child Process

Package source references child process execution.

src/workspace/fetch-npm-version.jsView on unpkg · L1

src/publish/utils.jsView file

27const run = (command, pkgDir) => { L28: execSync(command, { cwd: pkgDir, stdio: "inherit" }); L29: }; ... L34: L35: run("npx @vnejs/monorepo package --clean", pkgDir); L36: };

High

Runtime Package Install

Package source invokes a package manager install command at runtime.

src/publish/utils.jsView on unpkg · L27

Findings

3 High2 Low

HighChild Processsrc/workspace/fetch-npm-version.js

HighShell

HighRuntime Package Installsrc/publish/utils.js

LowScripts Present

LowFilesystem