T08 · Insecure Dependencies
- Location
SKILL.md:22- Finding
Unpinned Third-Party Package Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This appears to be a legitimate personal knowledge-base tool, but it deserves review because its optional server can allow unauthenticated persistent writes and its install command pulls unpinned external code.
Install only in an isolated environment, pin the package version yourself, and treat the web/API server as unsafe for shared networks unless you bind it to localhost or put it behind authentication and rate limits. Assume documents sent for compilation or asking may be transmitted to the configured LLM API.
SKILL.md:22Unpinned Third-Party Package Installation
SKILL.md:205Unauthenticated Persistent Write Operation on a Network-Exposed Service
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
mkdir my-kb && cd my-kb
cat > .env << 'EOF'
LLMBASE_API_KEY=sk-your-key
LLMBASE_BASE_URL=https://your-endpoint/v1
LLMBASE_MODEL=your-model
The description states that the LLM writes trilingual articles in EN / 中文 / 日本語 by default. This is a language/locale constraint presented as a default behavior rather than an explicit user-selected option, which can violate organizational policies requiring user choice for language preferences.
The security section makes an overbroad assurance that 'nothing is sent anywhere except the configured LLM API,' but the same skill explicitly supports fetching arbitrary URLs and corpus sources over the network. This is a security/privacy documentation flaw: users may underestimate outbound connections and data exposure paths, which can lead to unsafe deployment decisions or privacy misunderstandings.