iflow-engine-base@4.1.15
BIM Engine SDK for Vue2, Vue3, React and HTML
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged network behavior belongs to an optional BIM encoding feature: it reads component properties and sends them to DeepSeek only when its start method is called. Package metadata shows no install hook, and engine initialization only constructs the feature object.
Decision evidence
public snapshot- The package entry points load the BIM SDK bundles, and package.json declares no install lifecycle scripts.
- The DeepSeek API request is in an optional encoding method that reads BIM component properties; it is not invoked by the SDK constructor.
- The request sends those properties to api.deepseek.com using a key configured by the package, with an optional constructor override.
- The SDK initializes a OneClickEncoding instance when an engine is created.
- The optional encoding feature sends model property data to an external service when 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-D9NbR8ef.jsView on unpkg · L14234Findings
Affected versions and remediation
This report applies to iflow-engine-base@4.1.15.
See all versions of iflow-engine-base for other recorded verdicts.
- Review the evidence and your use of iflow-engine-base@4.1.15 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.