laravel-security-audit
Skill1 starsChanged 7 months agoMITView on GitHub
Security-Audit für Laravel-Apps. Nutze bei: "Security Audit", "Sicherheitsprüfung", "Go-Live Checkliste", "ist die App sicher", "Pre-Launch Check", "DSGVO-Check", "Security Hardening".
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- robiparvez/claude-code-guidelinestheir own version, first seen Aug 7, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- robiparvez/claude-code-guidelines★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- architectureSkill
- audit-projectSkill
- backendSkill
- deploySkill
- docs-structureSkill
- frontendSkill
- geoSkill
- git-commitSkill
- helpSkill
- init-projectSkill
- laravel-a11ySkill
- laravel-docsSkill
- laravel-performanceSkill
- laravel-testsSkill
- portfolio-texteSkill
- qaSkill
- requirementsSkill
- seoSkill
The file
Files
Laravel Security Audit
Allgemeine Security-Regeln → CLAUDE.md Kapitel 1 + 2. Dieser Skill fokussiert auf Audit-Methodik.
Severity Framework
| Level | Bedeutung | Zeitrahmen |
| KRITISCH | Muss vor Go-Live behoben sein | Sofort |
| HOCH | Ernstes Risiko | Innerhalb 1 Woche |
| MITTEL | Verbesserungspotenzial | Nächster Sprint |
| NIEDRIG | Best Practice | Backlog |
Workflow
- Automatisiert:
composer audit+npm auditfür Dependency-Checks - Manuell: Checkliste unten durchgehen
- Report: Priorisierte Findings mit konkreten Fixes
Checkliste
KRITISCH
Auth & Authorization:
- Alle sensiblen Routes durch Middleware geschützt? (
auth,verified,can:) - Rate-Limiting auf Login? (
throttleMiddleware) - Password-Hashing: bcrypt/argon2 (nie MD5/SHA1)
- Policies für Authorization (nicht
Gate::checkim Blade)
Injection:
- Kein rohes SQL – immer Query Builder / Eloquent
- Blade
{{ }}überall (kein{!! !!}ohne Grund) - Keine gefährlichen PHP-Funktionen mit User-Input
Environment:
APP_DEBUG=falsein ProductionAPP_ENV=production.envnicht in Git, nicht im Webroot- Keine Secrets in Code hardcodiert
HOCH
Mass Assignment: $fillable oder $guarded auf allen Models
CSRF: @csrf in allen Formularen
File Uploads: Typ-Validierung, Größenlimit, nicht in /public direkt
Session: secure, httponly, samesite=lax in config/session.php
API: Sanctum/Passport für Auth, Rate-Limiting auf allen Endpoints
Headers: X-Frame-Options, X-Content-Type-Options, Strict-Transport-Security
MITTEL
Dependencies: composer audit + npm audit – kritische sofort, Rest im nächsten Release
Logging: Keine Passwörter/IBAN/Keys loggen, IPs anonymisieren
Error Handling: Keine Stack-Traces in Production
DSGVO-spezifisch
Lösch-Routine (Anonymisierung statt hartem Löschen):
$user->update([
'name' => 'Gelöschter Nutzer',
'email' => "deleted_{$user->id}@example.com",
'phone' => null,
]);IP-Anonymisierung in Logs:
$anonymizedIp = preg_replace('/\d+$/', 'x', $request->ip());Prüfpunkte:
- Keine externen Ressourcen ohne Consent (Fonts, Analytics, CDN)
- Cookie-Consent vor Tracking-Code
- Datenschutzerklärung mit allen genutzten Diensten
Report-Format
# Security Audit – {Projekt} ({Datum})
## Zusammenfassung
{X} Kritisch, {Y} Hoch, {Z} Mittel
## Findings
| # | Severity | Kategorie | Finding | Datei | Empfehlung |
|---|----------|-----------|---------|-------|------------|
| 1 | KRITISCH | Auth | Routes ohne Middleware | routes/web.php | auth Middleware |Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

