Skip to content
Back to skills

Webapp Code Audit

ASecurity

Source-code security review and SAST triage for common vulnerability patterns.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
securitypythonrustgojavabashsqlgitapisecurity

Works with

  • api

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned November 7, 2026

npx -y skills add bitbytelabio/arsenal --skill webapp-code-audit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Webapp Code Audit?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Webapp Code Audit
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bitbytelabio-webapp-code-audit/badge)](https://www.skillsdirectory.com/skills/bitbytelabio-webapp-code-audit)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: webapp-code-audit
description: Source-code security review and SAST triage for common vulnerability patterns.
domain: webapp
category: compliance
hide: true
license: MIT
metadata:
  manifest_entry: src/corpus/webapp-code-audit/SKILL.md
---
# Source Code Security Audit

## ACTION REQUIRED (Execute immediately upon reading)

1. `NOW`: Read `skill://webapp-code-audit/support/field-journal/precedent-pentest.md` or code audit authorization.
2. `NOW`: Confirm **source code/repository access** (binary without source code → redirect to RE skill).
3. `NOW`: Clarify language stack and scope (directories/services/PR diff).
4. `NEXT`: tool-index; semgrep, etc.
5. `ACT`: Threat modeling draft → Automated scanning → Manual verification.

## Applicable Scenarios

- White-box audit, PR/diff security review
- SAST tools such as Semgrep / CodeQL / Bandit / gosec
- Dangerous APIs, injection points, missing authorization, cryptographic misuse
- Division of labor with `supply-chain-security/`: this skill focuses on **proprietary code logic**, while supply chain focuses on dependencies and pipelines

## Workflow

### 1. Scope and Threat Model

```text
□ Trust boundaries: User input, files, deserialization, SSRF, authentication/authorization middleware
□ High-value assets: Authentication, payments, admin consoles, key management
```

### 2. Automated Scanning

```bash
semgrep --config auto .
# Or project-specific rule packs
semgrep --config p/owasp-top-ten .
```

### 3. Manual Verification (MUST)

```text
□ Every SAST hit: Reachability? Exploitability? False positive?
□ Authorization: IDOR/privilege escalation, missing checks, flawed multi-tenant isolation
□ Injection: SQL/command/template/LDAP
□ Cryptography: Hardcoded keys, ECB mode, custom crypto
```

### 4. Deliverables

```text
Finding: Location + Data flow + PoC + Remediation recommendations
Optional ATT&CK / CWE identifiers
```

## Toolchain

| Tool | Language/Scenario |
|------|-------------------|
| Semgrep | Multi-language fast rule engine |
| CodeQL | Deep data flow analysis (GitHub) |
| Bandit | Python |
| gosec / staticcheck | Go |
| SpotBugs / FindSecBugs | Java |

## References

- `skill://webapp-code-audit/references/sast-review-checklist.md`
- ``skill://red-supply-chain-security`` ``skill://webapp-api-security`` ``skill://red-llm-security`` (Agent code)

## Routing Context

**Upstream**: MASTER R26  
**Role**: `skill://webapp-code-audit/support/ops/role-map.md` cae  
**Downstream**: Dependency vulnerabilities → supply-chain; Runtime verification → pentest-tools

## Task Completion Checklist

- [ ] Manually verified instead of merely pasting scanner outputs?
- [ ] Includes remediation recommendations?
- [ ] Confined strictly within the authorized repository scope?
- [ ] Checklist completed?

Files in this skill

  • SKILL.md2.8 KB
  • references/sast-review-checklist.md394 B
  • support/field-journal/precedent-pentest.md21.9 KB
  • support/ops/role-map.md4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.