Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
mia-trust
v1.0.0MIA-Trust Pipeline - Memory-Intelligent Assistant 信任守门+记忆进化 pipeline
⭐ 1· 30·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description (trust + memory pipeline) match the shipped code: planner, guard, memory, feedback modules are present and consistent with the declared purpose. However the registry metadata claims no required env vars/credentials while the code clearly expects multiple environment variables (MIA_PLANNER_API_KEY, MIA_TRUST_API_KEY, MIA_PLANNER_URL/MIA_TRUST_URL, model names, MIA_MEMORY_FILE, etc.). This is an incoherence between manifest and implementation.
Instruction Scope
SKILL.md instructs running local node scripts which in turn read and write local files (memory.jsonl, trust_experience.json), call other skill scripts, and make network requests to configurable LLM endpoints (defaults to api.openai.com). The runtime will persist user queries/outputs to local files and send user inputs/plan drafts to external endpoints when mode=api. The SKILL.md examples mention env vars but the registry didn't mark them required; instructions grant the skill discretion to read several env vars and local files beyond what the registry declared.
Install Mechanism
Install is a normal npm package (mia-trust) that declares node-fetch dependency from npm and a postinstall migration script. No opaque downloads, URL shorteners, or arbitrary remote archives are used. Creating a binary mia-trust that runs run.mjs is standard.
Credentials
The manifest declares no required credentials but the code requires (or can use) API keys and URLs for planner and trust LLM calls (MIA_PLANNER_API_KEY, MIA_TRUST_API_KEY, MIA_PLANNER_URL/MIA_TRUST_URL). Those env vars are named like SECRET/API_KEY and will be used to call remote LLM endpoints; this is proportionate to an LLM-based pipeline but the omission from the registry is a red flag. The skill also reads/writes local config/memory files (MIA_MEMORY_FILE, MIA_TRUST_EXPERIENCE_FILE), which may store sensitive user queries and outputs.
Persistence & Privilege
The skill is not always-enabled and doesn't modify other skills. It persistently stores memories, feedback, and trust_experience in local files under the skill directory by default; these records are retained on disk and could contain sensitive content. The agent can invoke the skill autonomously (default), which combined with storage and outbound API calls increases blast radius but is expected for such a pipeline.
What to consider before installing
Key things to check before installing or running this skill:
- Metadata mismatch: the registry says no env vars/credentials required, but the code expects API keys and endpoint URLs (MIA_PLANNER_API_KEY, MIA_TRUST_API_KEY, MIA_PLANNER_URL/MIA_TRUST_URL, etc.). Do not assume it runs without credentials; planner will exit if API mode is selected without keys.
- Outbound requests: by default the code will call configurable LLM endpoints (defaults to api.openai.com). Review and if needed override MIA_*_URL to a trusted internal endpoint before sending real data.
- Persistent storage: user queries, plans, evaluation results, and distilled experiences are written to local files (memory.jsonl, trust/trust_experience.json, feedback.jsonl). These files may contain sensitive content — restrict file permissions, or change paths via env vars (MIA_MEMORY_FILE, MIA_TRUST_EXPERIENCE_FILE, MIA_FEEDBACK_FILE) and/or run in an isolated environment.
- Source and provenance: package.json points to a placeholder GitHub URL (https://github.com/yourname/mia-trust). Confirm the package source/repo and review its upstream history before trusting it.
- Least-privilege: provide dedicated API keys with minimal scope, and run the skill in an isolated container or VM if you will process sensitive inputs.
- Review config: examine trust_experience.json and memory files shipped with the package (they may contain example data) and the SKILL.md/Pipeline documentation to understand what will be stored and sent externally.
- If you need guarantees: ask the author for a clear manifest update that lists required env vars/primary credential and the exact network endpoints the skill will contact; otherwise treat the mismatch as a risk. If unsure, run tests with synthetic non-sensitive inputs in a controlled environment first.run.mjs:53
Shell command execution detected (child_process).
planner/mia-planner.mjs:11
Environment variable access combined with network send.
trust/mia-trust.mjs:11
Environment variable access combined with network send.
trust/mia-trust.mjs:2
File read combined with network send (possible exfiltration).
Patterns worth reviewing
These patterns may indicate risky behavior. Check the VirusTotal and OpenClaw results above for context-aware analysis before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk97brjvb4fq3146d4k76az6dn1845mkf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🛡️ Clawdis
Binsnode
Install
Install mia-trust
Bins: mia-trust
npm i -g mia-trust