registry / aims-workstation / 0.1.11
aims-workstation@0.1.11
AIMS 工作站：本地智能体工作站——ARM 助手本地化（下载/离线/升级）、工作台对话式定制、多工作区隔离、分级自主与审计
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe inspected source shows the API key entered for the LLM configuration is sent to the configured endpoint, whose company-gateway default is disclosed in the UI. No source evidence established covert or unauthorized credential forwarding; the global TLS verification disablement is a security risk but does not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
The user configures the LLM in settings or starts the application with environment configuration.
Impact
No unauthorized credential transfer or other malicious impact was established. Disabling TLS verification does create a risk of interception for HTTPS requests.
Mechanism
The server creates an LLM provider using the configured base URL and API key; users can change the endpoint in settings.
AI rationale
The inspected source shows the API key entered for the LLM configuration is sent to the configured endpoint, whose company-gateway default is disclosed in the UI. No source evidence established covert or unauthorized credential forwarding; the global TLS verification disablement is a security risk but does not establish malicious behavior.
Evidence
package.jsonserver.jsbin/aims-workstation.jsweb/dist/assets/index-DsM_RyZ5.js.env.example.lpm-dependency-evidence-62c1f3e5-8f84-4263-8de9-ccc32fdc95ce/0/npm-linux/package.json.lpm-dependency-evidence-62c1f3e5-8f84-4263-8de9-ccc32fdc95ce/0/npm-linux/dist/index.js
Network endpoints1
bifrost.infra.dev.aimstek.cn/v1
Decision evidence
public snapshotAI called this Clean at 84.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI and has no install lifecycle hook.
- The configured LLM key is bound to the same base URL used for model requests; the default gateway is identified in the UI as the company gateway.
- The UI labels the field “API Key,” discloses the default gateway, and allows users to switch endpoints; the key is saved through the settings route.
- The example environment file uses a placeholder key value, not a real credential.
- The inspected dependency manifest has no install lifecycle hook, and its entrypoint consists of exports.
- Panel code is checked before storage; the inspected runtime operation logs validator warnings or rejects failed validation.
Evidence against
- The server disables TLS certificate verification globally, including for configured HTTPS endpoints.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
Source & flagged code
5 flagged.env.exampleView file
19patternName = npm_token
severity = critical
line = 19
Critical
19patternName = npm_token
severity = critical
line = 19
Critical
scripts/check-panel.mjsView file
20try {
L21: const factory = new Function('React', 'html', 'ui', 'useState', 'useEffect', 'useRef', 'useMemo',
L22: `"use strict";\n${code}\n;if (typeof Panel !== 'function') throw new Error('no Panel');\nreturn Panel;`);
Low
Eval
Package source references a known benign dynamic code generation pattern.
scripts/check-panel.mjsView on unpkg · L20Findings
2 Critical1 High4 Medium6 Low
CriticalCritical Secret.env.example
CriticalSecret Pattern.env.example
HighCredential Redirect Persistenceserver.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperscripts/publish-npm.sh
MediumStructural Risk Force Deep Review
LowScripts Present
LowEvalscripts/check-panel.mjs
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to aims-workstation@0.1.11.
See all versions of aims-workstation for other recorded verdicts.
- Review the evidence and your use of aims-workstation@0.1.11 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.