Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
spatie-security
seatplus/core
claude-code
security
csrf
authorization
database-security
server-hardening
credential-management
encryption

Apply Spatie's security guidelines when configuring applications, databases, or servers, or when reviewing code for security concerns; use for SSL setup, CSRF protection, password hashing, database permissions, and server hardening.

Install
php artisan boost:add-skill seatplus/core

Save this content to: .claude/skills/spatie-security/SKILL.md

# Spatie Security Guidelines

## Overview

Apply Spatie's security best practices when building, configuring, or reviewing applications and infrastructure.

## When to Activate

- Activate this skill when configuring application security (authentication, authorization, forms).
- Activate this skill when setting up or reviewing database configurations.
- Activate this skill when configuring servers or reviewing infrastructure.
- Activate this skill when reviewing code for security vulnerabilities.

## Scope

- In scope: Application security, database security, server configuration, credential management.
- Out of scope: Code style, business logic, UI/UX design.

## Application Security

- Transmit all HTTP traffic over SSL.
- Use CSRF tokens in all forms.
- Use appropriate HTTP methods for significant actions: `DELETE`, `POST`, `PUT` — never `GET`.
- Add automated authorization tests to verify only authorized users can access restricted functionality.

## Database Security

- Hash all stored passwords.
- Encrypt API keys stored in databases.
- Use separate database users per database with appropriate read/write permissions.
- Restrict database access to whitelisted hosts only (webserver and developer machines).

## Server Security

- Keep NGINX, PHP, Ubuntu, and similar software up to date.
- Use SSH with private key authentication; disable password authentication.
- Install and enable `unattended-upgrades` for automatic security updates.
- Configure firewalls to permit only necessary traffic (typically ports 22 and 443).
- Manage all servers through Ansible for rapid patching and access revocation.

## Credential Management

- Store all passwords in a password manager (e.g. 1Password).
- Ensure each password is unique; no reuse.
- Enable two-factor authentication when available.
- Protect all private keys with passwords.

## General

- Use backups (e.g. BackBlaze) and test them periodically.
- Enable FileVault (full-disk encryption) on all Macs.
- Never use public services like Pastebin for sensitive code or data.
- Install browser extensions only from official stores; minimize usage.

---

Source: https://spatie.be/guidelines/security

Spatie Security Guidelines

Overview

Apply Spatie's security best practices when building, configuring, or reviewing applications and infrastructure.

When to Activate

  • Activate this skill when configuring application security (authentication, authorization, forms).
  • Activate this skill when setting up or reviewing database configurations.
  • Activate this skill when configuring servers or reviewing infrastructure.
  • Activate this skill when reviewing code for security vulnerabilities.

Scope

  • In scope: Application security, database security, server configuration, credential management.
  • Out of scope: Code style, business logic, UI/UX design.

Application Security

  • Transmit all HTTP traffic over SSL.
  • Use CSRF tokens in all forms.
  • Use appropriate HTTP methods for significant actions: DELETE, POST, PUT — never GET.
  • Add automated authorization tests to verify only authorized users can access restricted functionality.

Database Security

  • Hash all stored passwords.
  • Encrypt API keys stored in databases.
  • Use separate database users per database with appropriate read/write permissions.
  • Restrict database access to whitelisted hosts only (webserver and developer machines).

Server Security

  • Keep NGINX, PHP, Ubuntu, and similar software up to date.
  • Use SSH with private key authentication; disable password authentication.
  • Install and enable unattended-upgrades for automatic security updates.
  • Configure firewalls to permit only necessary traffic (typically ports 22 and 443).
  • Manage all servers through Ansible for rapid patching and access revocation.

Credential Management

  • Store all passwords in a password manager (e.g. 1Password).
  • Ensure each password is unique; no reuse.
  • Enable two-factor authentication when available.
  • Protect all private keys with passwords.

General

  • Use backups (e.g. BackBlaze) and test them periodically.
  • Enable FileVault (full-disk encryption) on all Macs.
  • Never use public services like Pastebin for sensitive code or data.
  • Install browser extensions only from official stores; minimize usage.

Source: https://spatie.be/guidelines/security

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
uni-method/symfony-lib
tacticmedia/scim-server-bundle
neika-ai/symfony-bundle
mattleads/agent-publishing-bundle
glavweb/framework-bundle
glavweb/extra-bundle
glavweb/api-bundle
glavweb/admin-bundle
adachsoft/api-version-bundle
elsayed85/laravel-api-exceptions
ouhssini/laravel-demo-mode
daworks/ncloud-outbound-mailer-driver
gp247/cms
ignibyte/aic-gates
nexa-merchant/blog
novasa/laravel-language-center
opencage/geocode
adolfoholzer/parameters
livenetworks/ln-starter
cgv/localized-resource