iflow-engine-base@4.0.15
BIM Engine SDK for Vue2, Vue3, React and HTML
AI Security Review
scanned 10d ago · by lpm-firewall-aiStatic inspection found an embedded service credential in the distributed client, creating a risk of unauthorized reuse if it remains active. The model-data transfer is part of an explicit runtime feature, and the inspected source does not establish a separate attack.
Decision evidence
public snapshot- The client code supplies a built-in API key to the encoding helper and logs part of it when the helper is constructed.
- Calling the helper's start method collects selected model properties and submits them in chat requests to DeepSeek using that key.
- The helper is attached to the engine during construction, while the network transfer occurs in its separate start method.
- The inspected transfer is tied to an explicit runtime feature; it does not establish an install-time attack or theft of consumer credentials.
- The source does not establish whether the embedded service key is active or what access it permits.
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-DAEOqkkS.jsView on unpkg · L11724Findings
Affected versions and remediation
This report applies to iflow-engine-base@4.0.15.
See all versions of iflow-engine-base for other recorded verdicts.
- Review the evidence and your use of iflow-engine-base@4.0.15 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.