zova-cli-set-front@1.2.110
zova cli-set-front
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe manifest and distribution describe a project CLI with command-driven build and code-generation behavior. The scanner leads reviewed did not reveal install-time contact, credential collection, or unrelated execution.
Decision evidence
public snapshot- The package exports dist/index.js; its scripts build and clean generated CLI artifacts.
- The distribution exposes framework CLI commands and build, create, init, refactor, tools and OpenAPI functions.
- The changed REST template code adds schema rendering options by passing values to the existing schema helper.
- The manifest has no install, preinstall or postinstall hook; its lifecycle scripts are publishing and packing tasks.
- The distribution uses environment variables to name build output and optional copy destinations, and copies generated build files there.
- Narrow searches in dist/index.js found no fetch, child_process, eval or encoded-payload execution patterns.
Source & flagged code
6 flaggedTarball package.json differs from the npm registry version manifest for scripts or dependency sets.
package.jsonView on unpkgThe package exports dist/index.js; its scripts build and clean generated CLI artifacts.
package.jsonView on unpkg · L18Findings
Affected versions and remediation
This report applies to zova-cli-set-front@1.2.110.
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.110 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.