T08 · Insecure Dependencies
- Location
SKILL.md:10- Finding
Unpinned Third-Party SDK Receives API Credentials and User Data
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is coherent for building an AINative chat app, but its examples expose a server-funded chat API publicly without showing basic abuse, validation, or privacy controls.
Review before installing or using these examples in production. Pin the SDK version, verify the package source and publisher, protect or rate-limit /api/chat, validate request bodies and token usage, add quotas and monitoring, and clearly disclose that chat content is sent to AINative or its upstream model provider.
SKILL.md:10Unpinned Third-Party SDK Receives API Credentials and User Data
SKILL.md:20Unauthenticated Public Chat Route Allows Abuse of Server-Side API Credentials
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# .env.local
AINATIVE_API_KEY=ak_your_key
This markdown file documents server routes and client code that collect messages from users and transmit them via client.chat.completions.create(...) to an external AI service, but it does not warn users that chat content will leave their application environment. For markdown files, SQP-2 applies when the description omits warnings about behaviors affecting user data or privacy.