firebase-security-rules-auditor

Audits Firestore security rules against a penetration-testing checklist and returns a scored JSON report.

Updated May 5, 2026
One-click install
npx skills add https://github.com/nikegeorgian-stack/otgruzka-tovara --skill firebase-security-rules-auditor-nikegeorgian-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: firebase-security-rules-auditor
Source: https://github.com/nikegeorgian-stack/otgruzka-tovara/tree/main/.cursor/skills/firebase-security-rules-auditor
Command: npx skills add https://github.com/nikegeorgian-stack/otgruzka-tovara --skill firebase-security-rules-auditor-nikegeorgian-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Firestore security rules often look correct but contain subtle holes—update bypasses, self-assigned roles, missing size limits—that expose production data. This Skill applies a red-team audit methodology to find those vulnerabilities before attackers do. ## Core Features & Use Cases - Red-Team Audit Checklist: Systematically tests rules for update bypasses, authority-source flaws, business-logic mismatches, storage abuse, type safety, and field-level vs identity-level security gaps. - Scored Findings: Returns a structured JSON report with a 1-5 security score, severity-rated findings, and concrete fix recommendations. - Admin Bootstrapping Awareness: Correctly evaluates hardcoded admin email patterns without false positives when email verification is enforced. - Use Case: After updating firestore.rules for a production app, run this audit to confirm no user can escalate privileges, corrupt other users' documents, or exhaust storage before deploying. ## Quick Start Audit my Firestore security rules in firestore.rules and report any vulnerabilities with a security score.

Frequently Asked Questions about firebase-security-rules-auditor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Firestore security rules for vulnerabilities?▼

Audit Firestore rules by comparing create and update logic for bypass opportunities, verifying ownership checks on sensitive fields, and testing type and size validation. This Skill automates that red-team checklist and returns a scored JSON report with findings and fixes.

What are common Firestore security rules mistakes?▼

Common mistakes include trusting user-provided role fields, allowing updates that bypass create-time validation, missing string length limits enabling storage abuse, and using hasOnly() or diff() without ownership checks. Each maps to a specific severity level in the audit.

Is a hardcoded admin email in Firestore rules secure?▼

A single hardcoded admin email is acceptable if email_verified is also checked and no mechanism lets other users grant themselves admin. The audit does not penalize this pattern when those conditions hold, but flags escalation paths.

Why do Firestore rules pass testing but still leak data?▼

Rules can pass functional tests while allowing update bypasses, where a valid document is created then updated into a malicious state. Field-level restrictions without identity checks also let any authenticated user modify others' documents.

When should I run a Firestore security rules audit?▼

Run the audit whenever security rules are updated, before deploying to production, and after adding new collections or role logic. Catching rule flaws before deployment prevents unauthorized data access and privilege escalation.