audit-security

To audit security headers and authentication boundaries in SvelteKit and PocketBase, scan the web/src and backend/pb_hooks directories for anti-patterns and insecure storage. The audit applies a rubric to assess HTTP security headers, auth storage, and hook errors, generating a structured findings report.

Detect filter injection risks in PocketBase hooks by scanning backend/pb_hooks for vulnerable patterns and misconfigurations. The audit evaluates filter safety to identify injection vulnerabilities, ranking issues from Critical to Suggestion in the final findings report with file paths and line numbers.

The best way to check for hardcoded credentials in a SvelteKit and PocketBase stack is to run a security audit that scans source directories for exposed secrets. The audit identifies hardcoded credentials and outputs prioritized findings to guide pre-production risk mitigation.

This security audit works with SvelteKit and PocketBase projects that contain web/src and backend/pb_hooks directories. It evaluates your existing project structure to assess HTTP security headers, auth storage, filter injection, and hook errors without requiring external dependencies.

Security findings are ranked Critical, Warning, Suggestion, and Praise in the audit report. The structured output includes specific file paths and line numbers for each identified issue, providing prioritized guidance to mitigate risks before production deployment.