Back to plugin
Pluginv0.1.0

ClawScan security

HPC-AI · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

BenignApr 29, 2026, 6:50 AM
Verdict
benign
Confidence
high
Model
gpt-5-mini
Summary
The plugin's code, README, and runtime instructions are consistent with an OpenAI-compatible model provider that uses a single HPC_AI_API_KEY credential and the api.hpc-ai.com endpoint; nothing in the bundle requests unrelated secrets or installs arbitrary remote code.
Guidance
This plugin appears to be a straightforward OpenClaw provider for the HPC-AI MaaS. Before installing: 1) Be prepared to provide HPC_AI_API_KEY (the README, manifest and scripts require it). 2) Note the plugin will make network calls to api.hpc-ai.com (or whatever you set via HPC_AI_BASE_URL); only give it an API key you trust to use with that service. 3) The bundle includes source and compiled files — you can review scripts/live-smoke.mjs and the dist/ files to verify behavior. 4) The registry summary omitted the required env var; confirm the plugin manager will prompt for or store HPC_AI_API_KEY as you expect. If you plan to send sensitive data to models hosted off-site, consider privacy and data residency implications.

Review Dimensions

Purpose & Capability
okName, description, SKILL.md, openclaw.plugin.json and the source files all align: this is an OpenClaw provider that talks to an OpenAI-compatible HPC-AI endpoint. Declared provider id, model catalog, docs URL and the env var HPC_AI_API_KEY are used by the code. No unrelated services, binaries, or credentials are requested.
Instruction Scope
okSKILL.md only instructs how to install the plugin via ClawHub or from Git, and to set HPC_AI_API_KEY and optionally HPC_AI_BASE_URL. Runtime code and scripts (e.g., scripts/live-smoke.mjs) use only those environment variables and call the configured HPC-AI endpoints. There are no instructions to read unrelated system files, other credentials, or to transmit data to unexpected endpoints.
Install Mechanism
okThere is no remote download/install-from-URL step in SKILL.md; installation flows are standard (openclaw plugins install or pnpm dev workflow). The package includes source and built dist files but does not pull arbitrary archives or shorteners. The included pnpm lockfile lists many packages (mostly dev/transitive) but package.json has no runtime third-party dependencies beyond relying on the OpenClaw runtime — this is expected for a plugin.
Credentials
noteThe only credential referenced is HPC_AI_API_KEY (and an optional HPC_AI_BASE_URL). That is proportionate to a model-provider plugin. One minor inconsistency: the initial registry summary in the prompt lists 'Required env vars: none' while the plugin manifest, SKILL.md and code all expect HPC_AI_API_KEY — this appears to be a metadata omission in the registry snapshot rather than suspicious behavior in the code.
Persistence & Privilege
okThe plugin is not force-included (always: false) and uses normal OpenClaw plugin hooks. It does not request to modify other plugins or system-wide settings. Autonomous invocation (disable-model-invocation: false) is the platform default and appropriate for a provider plugin.