iflow-engine-base@4.0.16
BIM Engine SDK for Vue2, Vue3, React and HTML
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe source shows a user-invoked encoding feature that sends selected model properties to its configured provider, so it does not establish covert exfiltration or malicious intent. The default bearer-style key is embedded in the published bundle, creating unresolved exposure and possible unauthorized use if the key is valid; warn rather than block.
Decision evidence
public snapshot- The package entry points load the bundled SDK.
- The public OneClickEncoding API exposes start() and chat().
- The SDK embeds a bearer-style provider key as its default and logs part of it during initialization.
- Calling start() selects model elements, gathers coding properties, and sends batches to DeepSeek.
- The external request is part of the named encoding feature and runs through an explicit start() call.
- The inspected source does not establish that the embedded key is valid or that the transfer is hidden or install-triggered.
Source & flagged code
7 flaggedPackage source references a known benign dynamic code generation pattern.
dist/chunks/sdk-vendor-CVc1LiJj.jsView on unpkg · L2302Source contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/chunks/engine-3d-B0D38zLu.jsView on unpkg · L12802Findings
Affected versions and remediation
This report applies to iflow-engine-base@4.0.16.
See all versions of iflow-engine-base for other recorded verdicts.
- Review the evidence and your use of iflow-engine-base@4.0.16 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.