Skip to content

2001105254-netizen/RacePulsePH / .agents/skills/racepulse-security-prelaunch

racepulse-security-prelaunch

Verified

Run the 20-point RacePulsePH pre-launch security audit across secrets, Firebase rules, Functions auth, input validation, Storage uploads, response trimming and dependencies. Use before deploying Functions, Firestore or Storage rules, or public releases.

RacePulse pre-launch security sweep

Translate the 20-point pre-launch security checklist into concrete checks for Firebase Auth, Firestore, Cloud Storage, Cloud Functions (functions/) and the on-site LAN server (server.ts). This skill audits security posture and never relaxes racepulse-access.

Load with: racepulse-access, racepulse-access-validation. Rules upheld: C-2, C-4, C-5, R-02, R-33, R-35, R-36. Detail: 20-point mapping and evidence.

Checklist

CheckReasonEvidence
Keep server secrets (PAYMONGO_SECRET_KEY, PAYMONGO_WEBHOOK_SECRET, SMTP_APP_PASSWORD, AUTH_CODE_SECRET, RACEPULSE_BRIDGE_KEY) out of src/ and GitAny key in VITE_* or committed files is public to every browser userConfirm firebase.json ignores .secret* and .env* and grep src/ for secret key names
Use only the public Firebase web config in src/firebase.ts and enforce access in firestore.rules and storage.rulesFirebase web apiKey identifies the project; security depends on rules, not hiding firebase.tsRun npm run generate:access and npm run verify:rbac to test rules against the emulator
Verify Bearer ID tokens with admin.auth().verifyIdToken(token, true) and check accessPolicy.can(...) in every Function and LAN routeClient UI checks can be bypassed with direct HTTP requestsInspect requireUser in functions/index.js, requireRunner in functions/race-bib-claim-api.js and /api middleware in server.ts
Lock sensitive fields (role, approved, paymentStatus, bibNumber, accessHistory) against client tampering in firestore.rulesPrevents privilege escalation or fake paid registrations from the browser consoleInspect scripts/firestore-base.rules, firestore.rules and functions/index.js
Enforce rate limits and constant-time comparisons on verification codes, password resets, webhooks and bridge keysBlocks brute-force attacks on 6-digit codes and timing attacks on HMAC signaturesInspect rateLimit and crypto.timingSafeEqual in functions/account-security.js, functions/index.js and server.ts
Validate and bound all request payloads (safeText, numeric bounds, regex IDs, 8 KB limit on accountApi) and escape user contentRejects malformed or oversized inputs and prevents stored XSS in runner or team namesInspect registrationFromRequest in functions/index.js, readPayload in functions/race-bib-claim-api.js and functions/auth-api.js
Restrict Storage uploads by owner UID, role capability, MIME type and byte size (2 MB fonts, 8 MB images)Stops unauthorized file hosting or oversized uploads in Cloud StorageInspect storage.rules lines 30 to 41
Return minimal projections from APIs (publicPayment, safeRunner) so emergency contacts, RFID data and payment internals never leakPrevents accidental PII disclosure when a runner claims a bib or checks payment statusInspect publicPayment in functions/index.js and safeRunner in functions/race-bib-claim-api.js
Audit npm dependencies in root and functions/ before releaseCatches known vulnerabilities in transitive packagesRun npm audit --omit=dev at root and npm --prefix functions audit --omit=dev

Stack mapping

  • Row-level security in Supabase/SQL maps to firestore.rules, storage.rules and functions/access-policy.js.
  • Password hashing and session token signing are handled by Firebase Authentication; custom email verification and password reset codes are HMAC-SHA256 hashed in functions/account-security.js.

Not covered

  • Role preset design and rollout activation belong to racepulse-access and racepulse-access-validation.
  • Deep protocol and CORS/CSRF/SSRF reviews belong to racepulse-appsec-deep.

Verify

  1. Run npm run lint and npm run verify:rbac (when Java 21+ and Firebase CLI are present) or inspect the rule and Function files directly.
  2. Output the PASS/FAIL report covering all 20 items with concrete file and line evidence.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall