iflow-engine-base@4.1.11
BIM Engine SDK for Vue2, Vue3, React and HTML
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe reviewed external data flow is tied to an explicit AI encoding method that fits the BIM SDK’s purpose. The bundled API key is exposed in the published code, but the source does not show an attack or an automatic call.
Decision evidence
public snapshot- The package describes itself as a BIM Engine SDK and points to bundled runtime entry points.
- OneClickEncoding exposes start() and chat() as callable methods.
- start() gathers model properties and sends them in batches to the encoding function.
- The encoding function posts those inputs to api.deepseek.com and uses the response for encoding.
- The feature includes a hard-coded default DeepSeek API key, which is exposed in the published bundle.
- The model-property payload leaves the application for processing by the external DeepSeek service when the feature is invoked.
Source & flagged code
7 flaggedPackage source references a known benign dynamic code generation pattern.
distGaussian/gaussian.umd.jsView on unpkg · L1Source contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/chunks/engine-3d-DynpUTo4.jsView on unpkg · L14229Findings
Affected versions and remediation
This report applies to iflow-engine-base@4.1.11.
See all versions of iflow-engine-base for other recorded verdicts.
- Review the evidence and your use of iflow-engine-base@4.1.11 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.