Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
SpacetimeDB Memory
v1.1.7High-performance SpacetimeDB memory integration for OpenClaw. Replaces static file memory with a lightning-fast WebAssembly-powered mind-vault running on a l...
⭐ 0· 341·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (SpacetimeDB memory integration) matches the files and tools: SDK wrappers, store/search/edit/delete tools, and a legacy-import migration script. The npm dependency on the official 'spacetimedb' package is appropriate for this functionality.
Instruction Scope
Runtime instructions are narrowly scoped to connecting to a local SpacetimeDB instance and providing CRUD/search operations. The legacy-import.js script does read and overwrite workspace files (MEMORY.md, IDENTITY.md, etc.) — this is consistent with a migration tool but is destructive. The script requires an explicit --confirm flag and a direct workspace path; SKILL.md calls this out as a critical instruction. That safeguard reduces risk but the action remains sensitive and requires explicit user approval before execution.
Install Mechanism
Install is a standard npm install for the packaged Node project (package.json lists 'spacetimedb' dependency). No downloads from arbitrary URLs or extract-from-unknown-host steps are present. Note: SKILL.md/openclaw metadata includes an npm install step—this means dependencies will be pulled from the npm registry at install time.
Credentials
No required credentials or secret environment variables are requested. Optional env vars (SPACETIMEDB_URL and SPACETIMEDB_NAME) are consistent with configuring a local DB endpoint and name. The tools only reference those optional vars (or fall back to http://127.0.0.1:3001), so environment access is proportional.
Persistence & Privilege
The skill is not marked always: true and does not request system-wide privileges. It does include executable tools that the agent can invoke (normal). The only operation that writes files outside the skill folder is the legacy-import, which is destructive by design but requires an explicit invocation with --confirm; it's not listed as one of the automated tools, reducing accidental autonomous execution risk.
Assessment
This skill appears to do what it says: local SpacetimeDB memory CRUD and a migration helper. Before installing or running anything: 1) Run the provided 'npm install' in the skill directory only if you trust installing npm packages. 2) Ensure you run a local SpacetimeDB instance (default at http://127.0.0.1:3001) or set SPACETIMEDB_URL appropriately. 3) Do NOT run the legacy-import script unless you explicitly want your workspace files migrated — it will create .bak copies but will overwrite the originals; test on backups or a copy of your workspace first. 4) If you do not want the agent or tools to invoke destructive operations autonomously, avoid enabling broad autonomous invocation or run the skill only on-demand. 5) If you need higher assurance, review legacy-import.js and the .bak behavior in a sandboxed workspace before proceeding.package.json:39
Install source points to URL shortener or raw IP.
About static analysis
These patterns were detected by automated regex scanning. They may be normal for skills that integrate with external APIs. Check the VirusTotal and OpenClaw results above for context-aware analysis.Like a lobster shell, security has layers — review code before you run it.
latestvk97ay2vj745r23bzb18astgt2d82mjnn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🧠 Clawdis