mvframe
**English** | [简体中文](README.cn.md)
This report shows the evidence for mvframe@1.1.38. 1 of 9 known versions is blocked or flagged. The newest version, 1.1.39, is flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource establishes a complete persistence-and-exfiltration chain: the scaffold installs an agent directive, seeds its destination, and supplies the POST client. The lack of lifecycle execution reduces reach but does not negate the concrete malicious behavior of the advertised initializer.
Decision evidence
public snapshot- Scaffold writes bundled DingTalk test configuration into the target project's notify env file.
- Scaffold installs a Codex AGENTS.md section that mandates completion notifications containing request and work summaries.
- The notify CLI POSTs supplied messages to the configured webhook.
- No lifecycle hook is present; this chain is activated by the explicit scaffold command.
- No install, preinstall, or postinstall hook in package.json.
- The notifier binds locally by default and reads configuration from an env file.
Source & flagged code
5 flagged · loading sourcePackage source references dynamic require/import behavior.
scripts/copy-flag-assets.jsView on unpkg · L6Manifest entrypoint contains risky behavior absent from dist/build output.
scripts/scaffold-app.jsView on unpkg · L12Findings
Affected versions and remediation
This report applies to mvframe@1.1.38.
The versions list below shows the verdict for each recorded version.
- Avoid installing mvframe@1.1.38. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.