iflow-engine-base@4.1.19
BIM Engine SDK for Vue2, Vue3, React and HTML
AI Security Review
scanned 15h ago · by lpm-firewall-aiThe public encoding feature sends model properties to DeepSeek with a bundled key, without an evident user-configured service or key. The request is tied to an explicit feature call, so this is suspicious undisclosed external data handling rather than malicious automatic exfiltration.
Decision evidence
public snapshot- The encoding feature defaults to a hard-coded API key and `https://api.deepseek.com`.
- Its `start()` method collects model component properties and passes them as JSON to the chat method.
- The chat method POSTs that content to DeepSeek using the API key in a Bearer header.
- The package’s type declarations expose `OneClickEncoding.start()` as a callable method.
- The engine constructor creates the encoding feature, while the network request is reached through its `start()` flow.
- The package scripts shown are development, build, and test commands; no install lifecycle script is declared.
- The source ties the external request to a feature for generating model encodings, rather than an install-time or import-time data collection flow.
Source & flagged code
7 flaggedPackage source references a known benign dynamic code generation pattern.
dist/chunks/sdk-vendor-3G5leDKK.jsView on unpkg · L13713Source contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/chunks/EngineKernel-CHERjTSQ.jsView on unpkg · L7536Findings
Affected versions and remediation
This report applies to iflow-engine-base@4.1.19.
See all versions of iflow-engine-base for other recorded verdicts.
- Review the evidence and your use of iflow-engine-base@4.1.19 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.