registry / zova-cli-set-front / 1.2.120
zova-cli-set-front@1.2.120
zova cli-set-front
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe manifest exposes a build-tool entry point and declares no install hook. The changed REST code handles declaration dependencies and generated project output; the inspected code contains no unrelated network or credential flow.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Package code runs when imported or when its CLI commands are invoked; the REST build and copy behavior requires a build command.
Impact
No credential collection, unrelated network contact, or other malicious behavior was found in the inspected source.
Mechanism
The inspected code parses TypeScript declaration imports, resolves dependency versions from a project lockfile, and writes generated build output to project release or configured copy directories.
AI rationale
The manifest exposes a build-tool entry point and declares no install hook. The changed REST code handles declaration dependencies and generated project output; the inspected code contains no unrelated network or credential flow.
Evidence
project dist outputproject dist-releases/rest-${flavor}-${APP_VERSION}configured BUILD_REST_COPY_DIST directories
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exports dist/index.js as its library entry point.
- The only lifecycle hooks are prepublishOnly, prepack, and postpack; none is an install hook.
- The changed REST build code parses declaration imports and resolves dependency versions from the project lockfile.
- REST build output is written to configured project release and copy directories; the copy target is unset unless BUILD_REST_COPY_DIST is configured.
Evidence against
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 unpkg17"type": "module",
"exports": {
".": {
"types": "./dist/index.d.ts",
"default": "./dist/index.js"
},
"./package.json": "./package.json"
},
"publishConfig": {
"access": "public"
},
"scripts": {
"clean": "rimraf dist di
Low
Ai Review Evidence
The package exports dist/index.js as its library entry point.
package.jsonView on unpkg · L1728"scripts": {
"clean": "rimraf dist dist-cli tsconfig.build.tsbuildinfo tsconfig.cli.tsbuildinfo",
"tsc:publish": "npm run clean && node ../../../vona/packages-cli/cli/src/bin/vona.ts :bin:buildGeneral && tsc -p
Low
Suspicious Lifecycle Evidence
The only lifecycle hooks are prepublishOnly, prepack, and postpack; none is an install hook.
package.jsonView on unpkg · L28Findings
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 Evidencepackage.json
LowSuspicious Lifecycle Evidencepackage.json
LowSuspicious Dependency Evidencedist/index.js
LowAi Review Evidencedist/index.js
Affected versions and remediation
This report applies to zova-cli-set-front@1.2.120.
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.120 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.