registry / zova-cli-set-front / 1.2.122
zova-cli-set-front@1.2.122
zova cli-set-front
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package exposes CLI tooling for frontend builds and project-generation workflows. Its manifest shows build and publishing scripts rather than install hooks, and the flagged environment variables are used for build output configuration.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Commands run when explicitly invoked by the user; importing the package exposes its command catalog.
Impact
No harmful automatic behavior or unrelated data transmission was found in the inspected source.
Mechanism
The distribution implements build, project-generation, refactoring, metadata, and OpenAPI helpers. The inspected environment variable uses relate to build output paths.
AI rationale
The package exposes CLI tooling for frontend builds and project-generation workflows. Its manifest shows build and publishing scripts rather than install hooks, and the flagged environment variables are used for build output configuration.
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exports the built JavaScript entry point and declares build and publish scripts, with no install lifecycle hook shown.
- The distribution entry exports a catalog of CLI command groups, including tools and OpenAPI commands.
- The only environment variable references found are used to name a build output directory and select a build copy destination.
Evidence against
Behavioral surface
EnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
Source & flagged code
5 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 dist-cli tsconfig.build.tsbuildinfo tsconfig.cli.tsbuildinfo",
"tsc:publish": "npm run c
Low
Suspicious Lifecycle Evidence
The manifest exports the built JavaScript entry point and declares build and publish scripts, with no install lifecycle hook shown.
package.jsonView on unpkg · L17dist/index.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = zova-cli-set-front@1.2.106
matchedIdentity = npm:em92YS1jbGktc2V0LWZyb250:1.2.106
similarity = 0.896
summary = stored previous version shares package body but lacks this dangerous source file
Findings
1 Critical1 High1 Medium8 Low
CriticalManifest Confusionpackage.json
HighPrevious Version Dangerous Deltadist/index.js
MediumEnvironment Vars
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/index.js
LowAi Review Evidencedist/index.js
Affected versions and remediation
This report applies to zova-cli-set-front@1.2.122.
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.122 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.