@corva/create-app@0.122.0
Create an app to use it in CORVA.AI
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource inspection shows a user-invoked Corva app scaffolding and release CLI, not malware. Static hints arise from normal templates, credential configuration, archiving, and package-aligned network deployment.
Decision evidence
public snapshot- The CLI can upload a user-selected project archive to Corva during the explicit release command.
- Release reads API credentials from CLI options, environment, or the target project's .env.
- No preinstall, install, postinstall, prepare, or uninstall lifecycle hook is declared.
- The bin shim only launches this package's CLI with inherited terminal I/O.
- Network use is a documented Corva API client invoked by release/rerun flows.
- The flagged .env files are scaffold templates with an empty API_KEY, not embedded credentials.
- No eval, dynamic code loading, credential harvesting, AI-agent control writes, or stealth persistence was found.
Source & flagged code
5 flaggedPackage contains a critical-looking secret pattern.
common/node/.envView on unpkg · L1Package ships non-JavaScript build or shell helper files.
common/python/MakefileView on unpkgFindings
Affected versions and remediation
This report applies to @corva/create-app@0.122.0.
See all versions of @corva/create-app for other recorded verdicts.
- Review the evidence and your use of @corva/create-app@0.122.0 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.