Detect dangerous code patterns and insecure API usage in source code.
npx skills add https://github.com/NOMARJ/sigil --skill sharp-edges-nomarj
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
Identify risky API usage and insecure coding patterns in code, helping teams review safety before integration.
Run a code review to identify dangerous API usages and unsafe patterns across your project.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
kfolkesScan Python source code for security vulnerabilities using the Bandit linter.
Q16GDetect hard-coded secrets in code repositories and generate remediation guidance.
iani-kuliBlock hardcoded credentials and API keys during git commit workflows.
manuelbrandner85Scan software projects for security vulnerabilities using CodeQL data flow analysis.
