flavor-code@1.3.23
<p align="center"><a href="./README.md">English</a> | <b><a href="./README.zh-CN.md">简体中文</a></b></p>
AI Security Review
scanned 1mo ago · by lpm-firewall-aiSource inspection found a feature-rich, user-invoked coding application but no install lifecycle execution, self-dependency chain, covert collection, or default outbound reporting. The optional webhook reporter is disabled by default, so it does not establish malicious behavior.
Decision evidence
public snapshot- No npm install lifecycle hook is declared; the package exposes a desktop entry point and a CLI entry point.
- The CLI runs only when its executable is called and launches its bundled main program.
- The updater checks for a newer version before explicitly installing a newer global release of the same package.
- Incident reporting is disabled by default in both desktop and shared runtime code.
- The auxiliary chunk writes usage and audit records locally under the workspace .flavor directory.
- The cited Zod file is a normal vendored validation utility.
- No preinstall, install, or postinstall hook, runtime self-dependency, or automatic import-time network action was found.
- The only outbound incident reporter is disabled by default and requires configuration or an environment variable.
- No source evidence showed secret harvesting, covert persistence, destructive behavior, or an unconsented agent-control-surface write.
Source & flagged code
17 flagged · loading sourceFindings
Affected versions and remediation
This report applies to flavor-code@1.3.23.
See all versions of flavor-code for other recorded verdicts.
- Review the evidence and your use of flavor-code@1.3.23 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.