iflow-engine-base@3.12.19
BIM Engine SDK for Vue2, Vue3, React and HTML
AI Security Review
scanned 10d ago · by lpm-firewall-aiA fixed-looking DeepSeek key is embedded in the client bundle and used for requests to DeepSeek, creating credential exposure and possible reuse risk. The transfer requires invoking the encoding API, so the source supports a warning but not a package block.
Decision evidence
public snapshot- The shipped engine bundle contains a fixed-looking DeepSeek API key and uses api.deepseek.com as its default endpoint.
- Calling the encoding feature collects model component properties and posts them with that key to DeepSeek.
- The package exposes the feature through the engine API and a callable start method, so the transfer is user-invoked rather than an install-time action.
- The package manifest lists development and build scripts, with no install lifecycle hook.
- Source ties the external request to the encoding feature; inspected code does not send the key to an unrelated recipient.
- The manifest has no install lifecycle hook, and the SDK constructs the encoding helper without calling start.
Source & flagged code
8 flaggedPackage source references a known benign dynamic code generation pattern.
dist/Cesium/Workers/transcodeKTX2.jsView on unpkg · L25Package source references dynamic require/import behavior.
dist/draco/draco_decoder.jsView on unpkg · L7Findings
Affected versions and remediation
This report applies to iflow-engine-base@3.12.19.
See all versions of iflow-engine-base for other recorded verdicts.
- Review the evidence and your use of iflow-engine-base@3.12.19 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.