apollo-client-patterns
Audited by Socket on Feb 16, 2026
1 alert found:
Malware[Skill Scanner] Installation of third-party script detected All findings: [CRITICAL] command_injection: Installation of third-party script detected (SC006) [AITech 9.1.4] [CRITICAL] command_injection: Installation of third-party script detected (SC006) [AITech 9.1.4] [CRITICAL] command_injection: Installation of third-party script detected (SC006) [AITech 9.1.4] [HIGH] command_injection: Backtick command substitution detected (CI003) [AITech 9.1.4] [HIGH] command_injection: Backtick command substitution detected (CI003) [AITech 9.1.4] [HIGH] command_injection: Backtick command substitution detected (CI003) [AITech 9.1.4] [HIGH] command_injection: Backtick command substitution detected (CI003) [AITech 9.1.4] [HIGH] command_injection: Backtick command substitution detected (CI003) [AITech 9.1.4] This skill/documentation and code samples appear benign and consistent with the stated purpose of demonstrating Apollo Client patterns for React. There are no signs of malware, credential exfiltration, or hidden data flows to third-party domains. The primary security considerations are standard for client-side GraphQL apps: protecting auth tokens stored in localStorage against XSS, ensuring server-side validation/sanitization, and fixing minor code issues (missing gql import in one helper). Overall the content is safe to use as examples, with normal caveats about protecting localStorage tokens and validating inputs on the server.