high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: CLAUDE.md

Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.

CLAUDE.md:674 SecretsClaude instruction

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — supabase/functions/send-email/index.ts:36

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — supabase/functions/send-invite-email/index.ts:128

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — supabase/functions/send-welcome-email/index.ts:236

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.local.json

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/settings.local.json VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing

AI-coder instruction files were found, but the repo is missing license, ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.

Repo hardeningGenerated repo pattern

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/delete-account/index.ts:5

Found a known-risky pattern (cors_wildcard). Review and replace if possible.

supabase/functions/delete-account/index.ts:5 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/send-email/index.ts:7

Found a known-risky pattern (cors_wildcard). Review and replace if possible.

supabase/functions/send-email/index.ts:7 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/send-invite-email/index.ts:5

Found a known-risky pattern (cors_wildcard). Review and replace if possible.

supabase/functions/send-invite-email/index.ts:5 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/send-push/index.ts:15

Found a known-risky pattern (cors_wildcard). Review and replace if possible.

supabase/functions/send-push/index.ts:15 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/send-welcome-email/index.ts:7

Found a known-risky pattern (cors_wildcard). Review and replace if possible.

supabase/functions/send-welcome-email/index.ts:7 Cors wildcard

medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected

No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.

CI/CD securityCoverage

low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — src/views/Players.vue:166

A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…

Fq active light bg

low System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

Repo hardeningGenerated repo pattern

low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — src/App.vue:251