iflow-engine-base@4.1.2
⚠ Under reviewBIM Engine SDK for Vue2, Vue3, React and HTML
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe source shows an initialized encoding feature that sends requests to DeepSeek using a built-in key, but the inspected behavior does not establish an attack. Clean status requires citations for 372 distinct paths, exceeding the 256 citation limit, so the result remains unresolved.
Decision evidence
public snapshot- The engine creates its encoding helper during initialization and gives it a built-in API key.
- The helper sends chat requests with that key to the DeepSeek chat endpoint.
- The manifest lists development and build scripts but no npm lifecycle hook.
- The inspected request is part of the model encoding feature; these excerpts do not establish hidden collection or an attack.
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-6rggo3Ns.jsView on unpkg · L14150Findings
Affected versions and remediation
This report applies to iflow-engine-base@4.1.2.
See all versions of iflow-engine-base for other recorded verdicts.
- Review the evidence and your use of iflow-engine-base@4.1.2 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.