laravel-security
Laravel security best practices — authentication, authorization, Eloquent safety, CSRF, XSS prevention, API security, and secure deployment configurations. Use when reviewing Laravel auth, Eloquent safety, CSRF, XSS, API security, or deployment configuration.
68
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Security
2 findings: 1 high severity, 1 medium severity. You should review these findings carefully before considering using this skill.
W007: Insecure credential handling detected in skill instructions.
What this means
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
Why it was flagged
The skill includes literal secret-like values (e.g., APP_KEY, DB_PASSWORD, STRIPE_KEY=sk_live_...) and a command that injects secrets into the environment, which risks requiring the LLM to handle or reproduce secrets verbatim.
W009: Direct money access capability detected (payment gateways, crypto, banking).
What this means
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
Why it was flagged
The skill documentation explicitly references a payment gateway (Stripe) and includes code related to processing payments. Examples: the .env STRIPE_KEY entry and secret validation for services.stripe, the CSRF exclusion for stripe/* webhooks, a named rate limiter for 'payments', and a ProcessPaymentJob that "Process payment" and accepts paymentIntentId/cardFingerprint. These are specific payment-related artifacts (Stripe keys, webhook route, and payment processing job), which qualify as Direct Financial Execution capability.
- Repository
- affaan-m/ECC
- Commit
06c5e11
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.