iflow-engine-base@4.1.13
BIM Engine SDK for Vue2, Vue3, React and HTML
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package’s encoding feature sends selected BIM properties to an external AI service using a key embedded in the distributed bundle. Because the transfer is feature-related and requires an explicit method call, the evidence supports a warning about undisclosed external processing rather than a malicious verdict.
Decision evidence
public snapshot- The encoder embeds a DeepSeek API key in the package and logs its first eight characters when constructed.
- The public start() method gathers BIM component properties for encoding; this path is triggered by an explicit method call.
- The encoder posts those properties to api.deepseek.com using the embedded key.
- The remote request is part of the package’s BIM encoding feature and does not run merely on import.
- The reviewed flow sends selected component properties, rather than credentials belonging to the package user.
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/EngineKernel-CbL7CIqJ.jsView on unpkg · L7377Findings
Affected versions and remediation
This report applies to iflow-engine-base@4.1.13.
See all versions of iflow-engine-base for other recorded verdicts.
- Review the evidence and your use of iflow-engine-base@4.1.13 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.