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.
86 of your 143 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 88.22s for a 117.9 MB repo slow.
  • Repobility's analysis ran in 25.68s after the clone landed.

toeverything/AFFiNE

https://github.com/toeverything/AFFiNE · scanned 2026-06-05 08:38 UTC (5 days, 20 hours ago) · 10 languages

1552 raw signals (126 security + 1426 graph) 10/13 scanners ran 27th percentile · Typescript · huge (>500K LoC) System graph score 53 (higher by 25)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 55.0 0.20 11.00
documentation_score 70.0 0.15 10.50
practices_score 96.0 0.15 14.40
code_quality 80.0 0.10 8.00
Overall 1.00 77.9
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

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 4 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.
4 matching findings on this repo
  • low Old/deprecated-named symbol `withLegacy` in packages/frontend/core/src/modules/…
  • low Old/deprecated-named symbol `affine_permission_should_project_from_legacy` in p…
  • low Old/deprecated-named symbol `upsertLegacy` in packages/backend/server/src/model…
  • low Old/deprecated-named symbol `cleanupLegacy` in packages/backend/server/src/core…
View all legacy markers findings →
Commented-out code 49 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 (9 lines) in tests/affine-mobile/e2e/back-button-visibilit…
  • info Commented-code block (9 lines) in tests/affine-cloud-copilot/e2e/basic/chat.spe…
  • info Commented-code block (5 lines) in tests/affine-local/e2e/links.spec.ts:878
  • info Commented-code block (5 lines) in tests/affine-local/e2e/local-first-favorite-p…
  • info Commented-code block (6 lines) in tests/blocksuite/e2e/markdown.spec.ts:295
  • info Commented-code block (5 lines) in tests/blocksuite/e2e/format-bar.spec.ts:247
  • info Commented-code block (10 lines) in tests/blocksuite/e2e/drag.spec.ts:153
  • info Commented-code block (8 lines) in tests/blocksuite/e2e/utils/asserts.ts:614
  • info Commented-code block (5 lines) in tests/blocksuite/e2e/database/database.spec.t…
  • info Commented-code block (8 lines) in packages/frontend/i18n/src/i18next.ts:83
  • info Commented-code block (5 lines) in packages/frontend/apps/electron/src/main/wind…
  • info Commented-code block (8 lines) in packages/frontend/apps/electron/src/main/wind…
View all commented-out code findings →
Config drift 29 findings
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.
12 matching findings on this repo
  • high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c…
  • low File has no detected symbols: nyc.config.js
  • low File has no detected symbols: vitest.config.ts
  • low File has no detected symbols: tests/affine-cloud/playwright.config.ts
  • low File has no detected symbols: tests/affine-desktop/playwright.config.ts
  • low File has no detected symbols: tests/affine-mobile/playwright.config.ts
  • low File has no detected symbols: tests/affine-cloud-copilot/playwright.config.ts
  • info TODO/FIXME marker in shipping code — tests/affine-cloud/playwright.config.ts:30
  • info TODO/FIXME marker in shipping code — packages/frontend/apps/electron/vitest.con…
  • medium `dangerouslySetInnerHTML` used in a React component — packages/frontend/admin/s…
  • info TODO/FIXME marker in shipping code — packages/frontend/core/src/components/hook…
  • info TODO/FIXME marker in shipping code — packages/frontend/core/src/modules/at-menu…
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/afab7b39-e811-445c-b495-24ac5273d6de/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/afab7b39-e811-445c-b495-24ac5273d6de/

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.