sharp-edges

Scan JavaScript/TypeScript codebases for dangerous APIs and missing timeouts.

15|5|Updated May 17, 2026
One-click install
npx skills add https://github.com/cropsgg/skills --skill sharp-edges-cropsgg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharp-edges
Source: https://github.com/cropsgg/skills/tree/main/skills/engineering/sharp-edges
Command: npx skills add https://github.com/cropsgg/skills --skill sharp-edges-cropsgg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flag dangerous APIs and misconfigurations such as eval(), exec(), unsafe string interpolation in SQL or Shell, missing fetch timeouts, and use of process.exit() in library code, plus prototype pollution, so teams can surface risk before incidents.

Core Features & Use Cases

  • Scan codebases for dangerous function calls (e.g., eval, exec) and unsafe patterns across languages and project types.
  • Detect missing timeouts on external calls, and distinguish library code vs application code to guide remediation.
  • Surface potential prototype pollution and unsafe API usage; provide actionable flags for review.

Quick Start

Run a codebase audit to surface unsafe APIs and missing timeouts, and triage findings before deployment.

Frequently Asked Questions about sharp-edges

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan a JavaScript codebase for dangerous APIs and eval usage?

To scan a JavaScript codebase for dangerous APIs, run an audit to identify and flag unsafe patterns like eval, dynamic code execution, and shell or SQL command construction, producing a prioritized findings report for review.

How do I detect missing fetch timeouts in my TypeScript project?

You can detect missing fetch timeouts in a TypeScript project by scanning your codebase to surface external calls lacking timeouts, distinguishing between application and shared library code to guide remediation.

What is prototype pollution and how can I find it during a security audit?

Prototype pollution is an unsafe pattern where shared object prototypes are modified. You can find it during a security audit by scanning your codebase to surface potential prototype pollution and unsafe API usage.

Does the dangerous API scan distinguish between library code and application code?

Yes, the dangerous API scan distinguishes library code from application code to guide remediation, applying checks to JavaScript and TypeScript projects to appropriately contextualize shared utility behavior.

Why should I check for process.exit() in library code?

Checking for process.exit() in library code is necessary because shared utilities should not terminate the host application. Scanning flags this dangerous API usage so teams can surface risk before incidents occur.

What is the best way to audit unsafe string interpolation in SQL or Shell commands?

The best way to audit unsafe string interpolation in SQL or Shell commands is to scan the codebase for dangerous function calls and unsafe patterns, generating a prioritized findings report to triage before deployment.