sharp-edges

Detect dangerous code patterns and insecure API usage in source code.

5|2|Updated Feb 15, 2026

Search Tags:#static-analysis #code-review #risk-detection #software-security #code-security #dangerous-patterns

Ready to run

npx skills add https://github.com/NOMARJ/sigil --skill sharp-edges-nomarj

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sharp-edges
Source: https://github.com/NOMARJ/sigil/tree/main/packs/security/skills/owasp-security/sharp-edges
Command: npx skills add https://github.com/NOMARJ/sigil --skill sharp-edges-nomarj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify risky API usage and insecure coding patterns in code, helping teams review safety before integration.

Core Features & Use Cases

Dangerous Function Calls
SQL and Injection Vectors
Concurrency and Race Conditions
Path and File Operations
Cryptographic Footguns
Type and Memory Safety

Quick Start

Run a code review to identify dangerous API usages and unsafe patterns across your project.

Frequently Asked Questions about sharp-edges

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

FAQPage Schema

How do I identify dangerous code patterns and insecure API usage during a code review?▼

To identify dangerous code patterns during a code review, apply pattern-based static analysis to catch risky constructs like serialization hazards, concurrency issues, and cryptographic footguns before integration. It provides clear guidance on fixing these unsafe API usages across multiple languages.

What types of software security risks and injection vectors can static analysis detect in source code?▼

Static analysis detects software security risks like SQL injection vectors, dangerous function calls, race conditions, and path operation vulnerabilities. It scans source code to spot these insecure coding patterns and risky constructs before they reach production.

Does this static analysis tool work across multiple programming languages for security audits?▼

Yes, this static analysis tool works across multiple programming languages to support security audits and developer onboarding. It enforces pattern-based detection for dangerous API calls, memory safety issues, and cryptographic footguns regardless of the specific language used.

What is the best way to catch concurrency issues and race conditions before integrating new code?▼

The best way to catch concurrency issues and race conditions is to run pattern-based static analysis during the build or review phase. This detects unsafe threading constructs and risky API usage early, providing clear guidance to resolve concurrency hazards before integration.

How do I detect cryptographic footguns and memory safety issues in my project?▼

Detect cryptographic footguns and memory safety issues by running a project-wide code review using static analysis. This identifies insecure API usage and dangerous coding patterns related to cryptography and type safety, helping teams review safety before integration.

When should I use pattern-based risk detection instead of other code security tools?▼

Use pattern-based risk detection when you need to identify specific dangerous function calls and insecure coding patterns during code reviews or builds. It differs from broader security tools by targeting exact risky constructs like serialization hazards and injection vectors with clear, actionable guidance.