iflow-engine-base@4.1.17
BIM Engine SDK for Vue2, Vue3, React and HTML
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe AI encoding feature has a plausible reason to process model properties, and the transfer requires an explicit start() call. Because the package sends that project data to a hard-coded third-party service without a visible disclosure or consent step, treat it as a runtime data-sharing risk and warn rather than block.
Decision evidence
public snapshot- The engine creates a OneClickEncoding instance during initialization.
- Its start() method gathers matching model components and their properties, then sends batches for encoding.
- The chat request posts those batches to api.deepseek.com using a hard-coded bearer key.
- The package source does not show a disclosure or consent step explaining that model properties go to DeepSeek.
- The network request is reached through the explicit start() method; constructing the feature alone does not send model data.
- package.json declares no install, preinstall, or postinstall lifecycle script.
- Sending model properties to an AI service is consistent with the encoding feature’s purpose.
Source & flagged code
8 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-Bzn2f2uI.jsView on unpkg · L7526Findings
Affected versions and remediation
This report applies to iflow-engine-base@4.1.17.
See all versions of iflow-engine-base for other recorded verdicts.
- Review the evidence and your use of iflow-engine-base@4.1.17 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.