medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/export.ts:233

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/invite-user/index.ts:107

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/notify-admin-new-user/index.ts:41

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/launch.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/launch.json VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.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.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, tests. 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 quality Tests conf 1.00 CI is configured but no tests are detected

A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.

CI/CDConfig theaterRepo hardening

medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data

A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.

Mock dataCritical flowGenerated repo pattern

medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions

CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.

.github/workflows/deploy.yml CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/admin-update-user/index.ts:29

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

supabase/functions/admin-update-user/index.ts:29 Cors wildcard

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

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

supabase/functions/invite-user/index.ts:21 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/lib/supabase.ts:7

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

src/lib/supabase.ts:7 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in src/components/ImportDialog.tsx:264

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

src/components/ImportDialog.tsx:264 Domparser html parse

medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in src/components/IPTableImportModal.tsx:206

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

src/components/IPTableImportModal.tsx:206 Domparser html parse

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 108 placeholder/mock markers across 40 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

0 test file(s) for 114 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

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

Multiple low-cost hardening controls are missing together: license, tests. 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 cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned

actions/deploy-pages@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

.github/workflows/deploy.yml:50 CI/CD securitySupply chainGithub actions

low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — src/components/AdminSettings.tsx:171