registry  /  hn-workflow-components  /  1.1.0

hn-workflow-components@1.1.0

一个基于 React + TypeScript 的可视化工作流编排组件库，提供工作流编辑器与执行进度查看器两种模式。

AI Security Review

scanned 6d ago · by lpm-firewall-ai

No confirmed malicious attack surface was established. The package is a React workflow component library with user-invoked editor/viewer API calls to caller-configured backend endpoints.

Static reason
High-risk behavior combination matched malicious policy.
Trigger
Importing and rendering WorkflowComponents or WorkflowViewerComponents; save/publish/view actions trigger API calls.
Impact
Expected workflow data save, publish, load, and viewer status queries; no evidence of exfiltration or persistence beyond browser localStorage state.
Mechanism
React UI components with axios requests to workflow backend
Rationale
Static inspection shows package-aligned React workflow functionality; scanner hits are explained by bundled dependencies, axios, localStorage, and MSW artifacts. There is no lifecycle execution, covert endpoint, credential harvesting, shell/eval payload, or unconsented project/agent mutation.
Evidence
package.jsonREADME.mddist/workflow-components.es.jsdist/workflow-components.umd.jsdist/mockServiceWorker.jsdist/index.d.ts

Decision evidence

public snapshot
AI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for block
  • dist/workflow-components.es.js uses axios for workflow API calls configured from user prop baseUrl
  • dist/workflow-components.es.js uses localStorage key startNode and window.parent.postMessage on user publish action
  • dist/mockServiceWorker.js is a bundled stock MSW worker that can intercept fetch if separately registered
Evidence against
  • package.json has no install/preinstall/postinstall lifecycle hooks
  • main/module entrypoints export React workflow editor/viewer components, not install-time code
  • Network calls are relative workflow endpoints under caller-supplied baseUrl, matching README API contract
  • No child_process, fs access, credential harvesting, destructive behavior, or AI-agent control writes found
  • No bidi/Trojan Source controls found in dist entrypoints by byte-pattern search
  • mockServiceWorker.js is not referenced by package entrypoints or auto-registered
Behavioral surface
Source
ChildProcessEnvironmentVarsNetwork
Supply chain
HighEntropyStringsMinifiedUrlStrings
Manifest
NoLicense
scanned 3 file(s), 2.08 MB of source, external domains: ant.design, bit.ly, github.com, redux-toolkit.js.org, redux.js.org, styled-components.com, u.ant.design, www.styled-components.com, www.w3.org

Source & flagged code

2 flagged · loading source
dist/workflow-components.es.jsView file
37606contains invisible/control Unicode U+200C (zero width non-joiner) position: relative<U+200C>;
Critical
Trojan Source Unicode

Source contains bidi control or invisible Unicode characters associated with Trojan Source attacks.

dist/workflow-components.es.jsView on unpkg · L37606
dist/workflow-components.umd.jsView file
•Trigger-reachable chain: manifest.main -> dist/workflow-components.umd.js Reachable file contains a blocking source-risk pattern.
Critical
Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

dist/workflow-components.umd.jsView on unpkg

Findings

2 Critical3 Medium4 Low
CriticalTrojan Source Unicodedist/workflow-components.es.js
CriticalTrigger Reachable Dangerous Capabilitydist/workflow-components.umd.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License