flavor-code@1.3.18
<p align="center"><a href="./README.md">English</a> | <b><a href="./README.zh-CN.md">简体中文</a></b></p>
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource inspection shows a user-invoked coding agent with package-specific configuration persistence and opt-in reporting, but no automatic lifecycle execution or concrete malicious behavior. The static similarity signal is not substantiated by a source-level attack chain.
Decision evidence
public snapshot- When the CLI runs, it can copy configured model credentials into its package-specific configuration file.
- Optional incident reporting can include tool input, but it is disabled unless explicitly enabled.
- The manifest has no preinstall, install, or postinstall hook.
- The executable starts only when its CLI entry point is invoked.
- No self-dependency, concealed payload download, credential exfiltration endpoint, or foreign agent-control-surface mutation was found.
- The only built-in incident endpoint is localhost and reporting is opt-in.
Source & flagged code
21 flagged · loading sourceSource file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/cli-main.jsView on unpkgPackage source references shell execution.
Findings
Affected versions and remediation
This report applies to flavor-code@1.3.18.
See all versions of flavor-code for other recorded verdicts.
- Review the evidence and your use of flavor-code@1.3.18 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.