registry / zova-cli-set-front / 1.2.117
zova-cli-set-front@1.2.117
zova cli-set-front
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe manifest exposes a CLI command set and has no install hook. The reviewed file operations and environment-variable reads are part of explicit project build or code-generation commands, and no unrelated data collection or malicious behavior was identified.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
CLI command invocation; the package has no install-time hook and exports command definitions.
Impact
Expected project-local build and code-generation effects; no unexplained credential collection, unrelated network contact, or automatic account action was found.
Mechanism
Commands read project configuration and source files, then generate or update build outputs and framework files.
AI rationale
The manifest exposes a CLI command set and has no install hook. The reviewed file operations and environment-variable reads are part of explicit project build or code-generation commands, and no unrelated data collection or malicious behavior was identified.
Evidence
dist/index.jspackage.json
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exports dist/index.js, which defines and exports CLI commands rather than running a setup hook on import.
- Lifecycle scripts are limited to prepublishOnly and pack hooks; there is no install, preinstall, or postinstall script.
- The REST build command writes generated package metadata and release output as part of an explicit build operation.
- The inspected CLI dependency has its update check commented out and dispatches only after a command is invoked.
Evidence against
- The build command can remove or replace output directories and copy generated files, but these effects are tied to explicit build commands and project paths.
- The source reads APP_VERSION and BUILD_REST_COPY_DIST to name or route build outputs; the inspected code does not send their values over the network.
Behavioral surface
EnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedpackage.jsonView file
•devDependencies registry_only=clean-package,rimraf
Critical
Manifest Confusion
Tarball package.json differs from the npm registry version manifest for scripts or dependency sets.
package.jsonView on unpkg30"tsc:publish": "npm run clean && node ../../../vona/packages-cli/cli/src/bin/vona.ts :bin:buildGeneral && tsc -p tsconfig.build.json && tsc -p tsconfig.cli.json",
"prepublishOnly": "npm run tsc:publish",
"prepack": "clean-package",
"postpack": "clean-pac
Low
Suspicious Lifecycle Evidence
Lifecycle scripts are limited to prepublishOnly and pack hooks; there is no install, preinstall, or postinstall script.
package.jsonView on unpkg · L30dist/index.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = zova-cli-set-front@1.2.106
matchedIdentity = npm:em92YS1jbGktc2V0LWZyb250:1.2.106
similarity = 0.917
summary = stored previous version shares package body but lacks this dangerous source file
Findings
1 Critical1 High1 Medium9 Low
CriticalManifest Confusionpackage.json
HighPrevious Version Dangerous Deltadist/index.js
MediumEnvironment Vars
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowAi Review Evidencedist/index.js
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/index.js
LowSuspicious Dependency Evidence.lpm-dependency-evidence-1599f0e3-0b04-4a32-b59d-f0b23fabfaa8/0/npm-linux/dist/index.js
Affected versions and remediation
This report applies to zova-cli-set-front@1.2.117.
See all versions of zova-cli-set-front for other recorded verdicts.
- Review the evidence and your use of zova-cli-set-front@1.2.117 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.