sota-javascript-typescript
Pass
Audited by Gen Agent Trust Hub on Nov 6, 2026
Risk Level: SAFE
Full Analysis
- [SAFE]: The skill provides a comprehensive set of security rules and best practices for auditing and building JavaScript/TypeScript applications. The content focuses on defensive coding, strict type safety, and secure runtime configurations.\n- [SAFE]: All external URLs and references (e.g., Node.js release schedule, Vitest, PNPM, Sigstore) are directed toward reputable technology organizations and official documentation.\n- [SAFE]: The skill includes grep-based auditing probes designed to detect security flaws like unhandled floating promises, loose equality, and insecure DOM sinks. These are legitimate security tools and do not contain malicious code.\n- [SAFE]: Mentions of encoded characters (e.g., zero-width spaces or hanging fillers) are provided as examples for the agent to use in detection checklists, not as obfuscation within the skill's own instructions.\n- [INDIRECT_PROMPT_INJECTION]: The skill's primary function involves auditing user-provided code (untrusted data). This creates an inherent attack surface where the auditing agent might encounter malicious instructions in the code being reviewed. \n
- Ingestion points: User-provided code files (e.g., .ts, .js, .tsx) identified in SKILL.md.\n
- Boundary markers: None explicitly defined in the skill body for separating user code from instructions.\n
- Capability inventory: The agent is expected to use file reading and shell-based pattern matching (grep) across all project files.\n
- Sanitization: The skill strongly advocates for input parsing at application boundaries (e.g., using Zod), though the agent's auditing logic relies on pattern recognition rather than structural isolation.
Audit Metadata