thesongzhu/Friday

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.

44 of your 88 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

https://github.com/thesongzhu/Friday · scanned 2026-06-05 18:16 UTC (4 days, 20 hours ago) · 10 languages

972 raw signals (78 security + 894 graph) 11/13 scanners ran 42nd percentile · Typescript · large (100-500K LoC) System graph score 67 (higher by 6)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 20 hours ago · v2 · 446 actionable findings from 2 signal sources. 79 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 416 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	100.0	0.25	25.00
`testing_score`	42.0	0.20	8.40
`documentation_score`	65.0	0.15	9.75
`practices_score`	68.0	0.15	10.20
`code_quality`	70.0	0.10	7.00
Overall		1.00	73.1

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 23 Medium 91 Low 172 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 30 System graph 416 Crowd 0 Layer: Quality 318 Security 13 Cicd 3 Software 52 Frontend 41 Hardware 3 Api 16

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Legacy markers 5 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

5 matching findings on this repo

low Old/deprecated-named symbol `oauth_credentials_v010_legacy` in src/state/sqlite…
low Old/deprecated-named symbol `friday_reflex_candidates_v089_legacy` in src/state…
low Old/deprecated-named symbol `task_workflow_lanes_v082_legacy` in src/state/sqli…
low Old/deprecated-named symbol `friday_reflex_candidates_v091_legacy` in src/state…
low Old/deprecated-named symbol `scrubbedLegacy` in src/cli/friday-cli.ts:682

View all legacy markers findings →

Commented-out code 120 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (11 lines) in test/integration/hub/friday-phase24-trusted-…
info Commented-code block (8 lines) in test/integration/state/sqlite/friday-migratio…
info Commented-code block (5 lines) in test/integration/retry/friday-production-retr…
info Commented-code block (7 lines) in test/adversarial/privilege-escalation.test.ts…
info Commented-code block (9 lines) in test/adversarial/token-forgery.test.ts:73
info Commented-code block (5 lines) in test/adversarial/crypto-http-attacks.test.ts:…
info Commented-code block (5 lines) in test/adversarial/remediation-verification.tes…
info Commented-code block (8 lines) in test/unit/automation/openclaw-adoption/friday…
info Commented-code block (7 lines) in test/unit/hub/bootstrap/hub-helpers.test.ts:2…
info Commented-code block (6 lines) in test/unit/hub/bootstrap/friday-durable-memory…
info Commented-code block (5 lines) in test/unit/api/http/friday-http-server-default…
info Commented-code block (5 lines) in test/unit/api/http/routes/friday-channel-webh…

View all commented-out code findings →

Config drift 1 finding

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

1 matching finding on this repo

low File has no detected symbols: vitest.config.ts

View all config drift findings →

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/c5fba84f-b81a-4bdf-84b5-d36dbead92d4/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c5fba84f-b81a-4bdf-84b5-d36dbead92d4/

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.