Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Personaldatahub
v0.1.0Pull personal data (emails, issues) and propose outbound actions (drafts, replies) through the PersonalDataHub access control gateway. Data is filtered, reda...
⭐ 0· 422·0 current·0 all-time
byHaojian Jin@haojian
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The plugin's code (dist/*) implements a client and tools to pull data and propose actions via a PersonalDataHub HTTP API — this aligns with the description. However, the registry metadata declares no required env vars or credentials while the code supports/reads PDH_HUB_URL, PDH_API_KEY, and ~/.pdh/credentials.json (config resolution). That mismatch between declared requirements and actual config resolution is unexpected and should be clarified.
Instruction Scope
SKILL.md and the code instruct the agent/installer to read and write files under ~/.pdh (config/credentials), probe localhost URLs, create API keys via POST /api/keys, and start a local server (npx pdh start or node dist/index.js). These actions go beyond simple read-only queries: they create credentials, persist configuration to disk, and start background services — all of which are within the skill's purpose but are sensitive operations that the skill did not advertize in the registry metadata.
Install Mechanism
There is no registry-level install spec, but SKILL.md includes an 'install' command that runs: cd ../../ && pnpm install && pnpm build && npx pdh init "OpenClaw Agent" && npx pdh start. Running pnpm in a parent directory (cd ../../) is unusual and risky (may install dependencies outside the plugin sandbox). The install flow writes config (~/.pdh), builds code, and starts a server — this will write files and run code locally. No external, untrusted download URLs are present, but the install performs non-trivial disk and process operations.
Credentials
The package does not declare required env vars in registry metadata, yet the runtime code checks PDH_HUB_URL and PDH_API_KEY, reads ~/.pdh/credentials.json, and can auto-create API keys. The plugin also logs auto-created API keys via api.logger.info, which risks leaking secrets into logs. Asking for or creating an API key and then printing it is disproportionate unless the user explicitly expects/consents to local key creation and understands logging implications.
Persistence & Privilege
The skill does not request always:true; it registers tools and appends a system prompt via a before_agent_start hook (normal behaviour for a data-access plugin). The main privilege is that the skill can auto-discover localhost, create API keys, persist credentials to ~/.pdh, and start a local server — persistent artifacts are created on disk and a background service may be started during install. That persistence is expected for a local gateway, but it is a noticeable system presence and should be consented to by the user.
What to consider before installing
What to consider before installing this skill:
- Confirm source and trust: The skill's homepage points to a GitHub repo; review that repo and its history before installing. The package will build and may start a local server and create local credentials.
- Expect writes and processes: The SKILL.md install steps run pnpm build and npx pdh init/start, which will write config and credentials under ~/.pdh and start a background HTTP service on localhost. If you do not want services started or files written to your home directory, do not run the install commands.
- Environment/credentials mismatch: Although the registry lists no required env vars, the code reads PDH_HUB_URL and PDH_API_KEY and ~/.pdh/credentials.json. If you install, verify where API keys and hub URLs are stored and who can read them.
- Secret leakage risk: The plugin logs auto-created API keys (api.logger.info). If you allow auto-creation, the key may be emitted to agent logs. Consider rotating/deleting any auto-created key or inspecting logs for exposure.
- Install in a sandbox first: Because the install uses pnpm at a parent path (cd ../../) and starts a server, run the install and server inside a container, VM, or isolated environment to confirm behavior before adding it to a production/local agent.
- Verify 'cd ../../' intent: The install line's cd ../../ is unusual (it moves out of the plugin directory) — ask the author why this is necessary and whether the command should be run from a particular repository layout.
- Prefer explicit configuration: Instead of relying on auto-discovery/auto-creation, consider configuring hubUrl and apiKey explicitly (or set environment variables) so you control where credentials are created and stored.
If you want more assurance, ask the maintainer for a detailed install guide, a signed release, or run a code review of the npx pdh package and the repo's build artifacts before enabling the skill in your agent.Like a lobster shell, security has layers — review code before you run it.
latestvk97bm2bs85q1wf9e7m8nqw1v1981v9vy
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
