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
29 of your 70 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 16.36s · analysis 7.5s · 49.1 MB · GitHub API rate-limit (preflight)

obsidian-tasks-group/obsidian-tasks

https://github.com/obsidian-tasks-group/obsidian-tasks · scanned 2026-06-05 20:51 UTC (4 days, 13 hours ago) · 10 languages

311 raw signals (61 security + 250 graph) 11/13 scanners ran 98th percentile · Typescript · large (100-500K LoC) System graph score 64 (higher by 26)

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

Complete repo analysis

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

JSON
Combined
78.0
/100
Security checks
92
27 findings
System graph
64
77.8% cov · 115 findings
Critical
1
click to filter
Agents
6
0 votes
Crowd
0
reported
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 100.0 0.20 20.00
documentation_score 84.0 0.15 12.60
practices_score 85.0 0.15 12.75
code_quality 70.0 0.10 7.00
Overall 1.00 90.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 1 High 0 Medium 10 Low 66 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 27 System graph 115 Crowd 0 Layer: Quality 41 Security 4 Software 54 Cicd 2 Api 1 Frontend 36 Network 4

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.

Commented-out code 19 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 (7 lines) in tests/ui/EditableTask.test.ts:224
  • info Commented-code block (5 lines) in tests/Query/Filter/DescriptionField.test.ts:36
  • info Commented-code block (8 lines) in src/Obsidian/LivePreviewExtension.ts:115
  • info Commented-code block (6 lines) in src/Scripting/ExpandPlaceholders.ts:139
  • info Commented-code block (6 lines) in src/ui/DependencyHelpers.ts:44
  • info Commented-code block (14 lines) in src/Query/QueryFileDefaults.ts:33
  • info Commented-code block (8 lines) in src/Query/Filter/BooleanPreprocessor.ts:23
  • info Commented-code block (5 lines) in src/Query/Filter/FunctionField.ts:310
  • info Commented-code block (5 lines) in src/Query/Matchers/RegexMatcher.ts:30
  • info Commented-code block (10 lines) in src/lib/logging.ts:225
  • info Commented-code block (6 lines) in src/lib/RegExpTools.ts:6
  • info Commented-code block (6 lines) in src/Config/Settings.ts:224
View all commented-out code findings →
Config drift 9 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.
9 matching findings on this repo
  • low File has no detected symbols: jest.config.js
  • low File has no detected symbols: jest.integration.config.js
  • low File has no detected symbols: svelte.config.js
  • low File has no detected symbols: i18next-parser.config.js
  • info TODO/FIXME marker in shipping code — src/Config/Settings.ts:188
  • info TODO/FIXME marker in shipping code — src/Config/PresetsSettingsUI.ts:377
  • info TODO/FIXME marker in shipping code — src/Statuses/StatusConfiguration.ts:69
  • info Commented-code block (6 lines) in src/Config/Settings.ts:224
  • info Commented-code block (5 lines) in src/Config/CustomStatusModal.ts:164
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/8e99b1a9-d2ca-409a-82ad-1347c5dd3629/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/8e99b1a9-d2ca-409a-82ad-1347c5dd3629/

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.