iflow-engine-base@4.1.9
BIM Engine SDK for Vue2, Vue3, React and HTML
AI Security Review
scanned 5d ago · by lpm-firewall-aiThis BIM SDK’s DeepSeek request is part of its encoding feature and runs when that feature is started, rather than automatically on installation or import. The bundled API key is exposed and partially logged, but the reviewed code does not show it being used for unrelated actions.
Decision evidence
public snapshot- The manifest describes a BIM engine SDK and has no install lifecycle scripts.
- The engine creates a OneClickEncoding helper as part of engine setup; its encoding work is initiated by calling start().
- The encoding method sends selected model component data to DeepSeek for encoding.
- The helper contains a hard-coded API key and logs its first eight characters when constructed.
- The package sends model data to api.deepseek.com when encoding is started.
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-cz2yEP2W.jsView on unpkg · L14213Findings
Affected versions and remediation
This report applies to iflow-engine-base@4.1.9.
See all versions of iflow-engine-base for other recorded verdicts.
- Review the evidence and your use of iflow-engine-base@4.1.9 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.