Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.
Sign up free Scan another repo

uncfreak1255-code/seascape-vacations-site

https://github.com/uncfreak1255-code/seascape-vacations-site · scanned 2026-06-16 02:48 UTC (2 months, 1 week ago)

210 raw signals (0 security + 210 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v4 · 100 actionable findings from 1 signal source. 5 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
23.5
/100
Security checks
24
0 findings
System graph
24
77.8% cov · 100 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 3 Medium 40 Low 50 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 100 Crowd 0 Layer: Software 1 Frontend 36 Network 2 Security 27 Cicd 1 Quality 30 Api 3
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 23.5/100 with 77.8% coverage. It contains 2045 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 105 findings — concentrated in frontend (36), quality (30), security (27). Risk profile is high: 0 critical, 3 high, 40 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 87 of 100 actionable findings. 105 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: GET /.netlify/functions/get-properties (scripts/enforcement/lib.test.js:123)
`scripts/enforcement/lib.test.js:123` calls `GET /.netlify/functions/get-properties` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/.netlify/functions/get-properties` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (scripts/evals/lib/anthropic-client.js:31)
`scripts/evals/lib/anthropic-client.js:31` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an external API, p…
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'exec_used' in scripts/evals/lib/targets.js:123
Found a known-risky pattern (exec_used). Review and replace if possible.
scripts/evals/lib/targets.js:123 Exec used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/enforcement/lib.test.js:123
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 — scripts/enforcement/serve-static.test.js:27
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 — scripts/evals/lib/anthropic-client.js:31
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 — src/assets/js/conversion-tracking.js:592
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 — src/assets/js/hero-v2.js:101
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/agents/seo-architect.md
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/agents/seo-architect.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/agents/voice-editor.md
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/agents/voice-editor.md 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 authority lacks a verifier contract: plugins/seascape-seo-os/skills/internal-link-targeting/SKILL.md
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.
plugins/seascape-seo-os/skills/internal-link-targeting/SKILL.md VerificationSkill file
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. 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 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 security security conf 1.00 Insecure pattern 'cors_wildcard' in DEPLOY THIS FOLDER TO NETLIFY/netlify/functions/get-properties.js:61
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
DEPLOY THIS FOLDER TO NETLIFY/netlify/functions/get-properties.js:61 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/js/dashboard.js:287
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/js/dashboard.js:287 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in DEPLOY THIS FOLDER TO NETLIFY/index.html:325
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
DEPLOY THIS FOLDER TO NETLIFY/index.html:325 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in DEPLOY THIS FOLDER TO NETLIFY/properties/index.html:2969
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
DEPLOY THIS FOLDER TO NETLIFY/properties/index.html:2969 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in index.html:5291
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
index.html:5291 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in scripts/recovery/assert-build-output.js:234
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
scripts/recovery/assert-build-output.js:234 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/assets/js/hero-v2.js:344
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/assets/js/hero-v2.js:344 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in eleventy.config.js:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
eleventy.config.js:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/enforcement/build-site.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/enforcement/build-site.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/enforcement/capture-visual-proof.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/enforcement/capture-visual-proof.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/enforcement/claude-content-gate.js:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/enforcement/claude-content-gate.js:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/enforcement/create-release-scorecard.js:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/enforcement/create-release-scorecard.js:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/enforcement/graveyard-prune.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/enforcement/graveyard-prune.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/enforcement/install-hooks.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/enforcement/install-hooks.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/enforcement/pre-commit.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/enforcement/pre-commit.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/enforcement/pre-push.js:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/enforcement/pre-push.js:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/enforcement/repo-hygiene.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/enforcement/repo-hygiene.js:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/enforcement/verify-release.js:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/enforcement/verify-release.js:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/enforcement/worktree-lock.js:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/enforcement/worktree-lock.js:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/evals/lib/targets.js:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/evals/lib/targets.js:3 Node child process
medium System graph network Security conf 1.00 Privileged port 10 in use
Port 10 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/live-smoke.yml Ports
medium System graph network Security conf 1.00 Privileged port 17 in use
Port 17 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/live-smoke.yml Ports
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
low System graph quality Integrity conf 1.00 24 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ANTHROPIC_API_KEY`, `CI`, `GITHUB_ACTIONS`, `GUEST_EMAIL_CAPTURE_BLOBS_SITE_ID`, `GUEST_EMAIL_CAPTURE_BLOBS_TOKEN`, `GUEST_EMAIL_CAPTURE_METRICS_TOKEN`, `MAILCHIMP_AUDIENCE_IDS`, `NETLIFY_AUTH_TOKEN` + 16 more. Add them (with a placeholder/comment…
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 130 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 6 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 6 locations
.github/workflows/live-smoke.yml:21, 24 (2 hits)
.github/workflows/playwright-visual.yml:41, 48 (2 hits)
.github/workflows/release-safety.yml:18, 23 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence
The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.
Governance
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `absoluteLegacy` in scripts/guides/normalize-guides.js:203
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `guest_email_capture_metrics_v1` in netlify/functions/_guest-email-capture-metrics.js:5
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `guest_email_capture_metrics_v1` in scripts/enforcement/guest-email-capture-receipts.test.js:231
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `owner_lead_metrics_v1` in netlify/functions/_owner-lead-contacts.js:5
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `owner_lead_metrics_v1` in netlify/functions/_owner-lead-metrics.js:3
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `owner_lead_metrics_v1` in scripts/enforcement/owner-lead-receipts.test.js:129
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `properties_cache_v1` in src/_data/properties.js:9
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: repl
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
DEPLOY THIS FOLDER TO NETLIFY/scripts/fix_vacationrental_schema.py:157
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — dashboard/js/dashboard.js:466
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — DEPLOY THIS FOLDER TO NETLIFY/scripts/cache-headers-tests.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — DEPLOY THIS FOLDER TO NETLIFY/scripts/property-card-tests.js:18
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — DEPLOY THIS FOLDER TO NETLIFY/scripts/seo-guides-tests.js:36
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/archive/sync-props.js:22
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/cache/sync-hostaway-build-cache.js:68
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/enforcement/capture-visual-proof.js:36
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/enforcement/create-release-scorecard.js:22
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/enforcement/generate-release-scorecard.js:37
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/enforcement/graveyard-prune.js:432
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/enforcement/install-hooks.js:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/enforcement/owner-proof-freshness.js:69
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/enforcement/pre-push.js:80
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/enforcement/repo-hygiene.js:112
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/enforcement/serve-static.js:206
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/enforcement/sync-next-batch-from-analytics-receipt.js:192
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/enforcement/validate-internal-links.js:303
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/enforcement/validate-jsonld.js:217
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/enforcement/validate-properties-availability-output.js:57
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/enforcement/validate-redirect-targets.js:184
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/enforcement/verify-release.js:258
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/evals/extract-copy.test.js:41
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/evals/lib/run-lane.js:50
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/evals/lint-evals.js:49
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/guides/normalize-guides.js:348
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/guides/upgrade-priority-guides.js:267
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/pull-property-truth.js:225
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/recovery/assert-build-output.js:561
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/recovery/assert-direct-booking-event-smoke.js:375
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/recovery/assert-live-entity-schema-coverage.js:162
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/recovery/assert-live-smoke.js:202
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/recovery/assert-owner-funnel-routes.js:81
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/regenerate-property-surfaces.js:250
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/seo/generate-pseo-triage.js:279
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/seo/import-dataforseo-findings.js:381
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: GET /*.html
`scripts/enforcement/release-cache-policy.js` declares `GET /*.html` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/071e7f5e-5af7-4a8b-86c3-33f3f76af7d1/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/071e7f5e-5af7-4a8b-86c3-33f3f76af7d1/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.