Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Semantic Grep
v1.0.0Offline local semantic code search using embeddings to find and index code by meaning with llama.cpp, ONNX, or Ollama backends.
⭐ 0· 79·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
The name/description (local semantic code search using local LLM/ONNX/Ollama backends) aligns with the instructions to run a CLI that indexes and searches projects. Optional environment variables for model paths/backends are consistent with that purpose. Minor concern: the CLI command shown is 'semgrep', which collides with the well-known 'semgrep' tool — that could cause confusion or unintended overwriting of an existing tool.
Instruction Scope
SKILL.md contains straightforward runtime instructions (index/search/list/remove) that operate on local paths, which is expected. It claims '100% offline' which is plausible but not verifiable from the instruction-only content (the listed pip package could perform network operations at install/runtime). The README includes a 'clh skill install' example containing a token-like string — this is out-of-scope for the skill's functionality and is a red flag (exposes a credential in a public file).
Install Mechanism
There is no registry install spec; the docs advise 'pip install semgrepll'. Installing an unreviewed pip package is a common but non-trivial risk because package install or imported code can execute arbitrary actions. The installers and clawhub.yaml consistently point to pip installation and a GitHub repository, which is coherent, but there is no baked-in, auditable code in the skill bundle for review (instruction-only).
Credentials
The SKILL.md lists optional environment variables (model paths, backend selection) that are proportional to running a local embedding/indexing tool. However, the README contains an apparent ClawHub token in an example command — a likely hard-coded secret that is unrelated to the skill's core behavior and should not be present in public docs. Also, no required credentials are declared in the registry metadata, which is consistent with the instructions, but the hidden token in docs is concerning.
Persistence & Privilege
The skill is not marked 'always' and does not request persistent system-wide privileges in the provided files. It's instruction-only and does not declare modifications to other skills or agent-wide settings.
Scan Findings in Context
[hardcoded_secret_in_readme] unexpected: README.md contains a ClawHub install example with a token-like string ('clh_kGzZkmMzlFFQOG7wuuZRMFmZkmlrelVNUrbZ1LvR0xA'). Publishing an install token or secret in public docs is inappropriate and unrelated to the skill's core function.
What to consider before installing
Before installing: (1) Treat the package as untrusted until you inspect its source—pip installing runs code that can do anything on your system. (2) Verify the PyPI package and GitHub repository referenced (rizperdana/semgrepll) and inspect the package contents or prefer building from source. (3) Remove or rotate any tokens you find in docs (the README includes a token-like string) and do not reuse it. (4) Consider running the install in a sandboxed environment or VM, or inspect the package with tools like 'pip download' and review the wheel/tarball. (5) Be cautious about the 'semgrep' command name collision—ensure it won't override or confuse an existing semgrep installation. If you want help, provide the actual PyPI package/source code and I can re-evaluate the install-time behavior and look for network calls or unsafe operations.Like a lobster shell, security has layers — review code before you run it.
latestvk97706v7jnqwh5vv0fk980b5c983f11z
License
MIT-0
Free to use, modify, and redistribute. No attribution required.