wekan/wekan

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.

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 32.42s for a 59.5 MB repo slow.
Repobility's analysis ran in 9.17s after the clone landed.

https://github.com/wekan/wekan.git · scanned 2026-05-22 09:04 UTC (2 weeks ago) · 10 languages

849 findings (183 legacy + 666 scanner) 11/13 scanners ran 44th percentile · Javascript · large (100-500K LoC) Scanner says 55 (higher by 21)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks ago · v2 · 516 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

100.0% cov · 333 gaps

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`	39.0	0.20	7.80
`documentation_score`	90.0	0.15	13.50
`practices_score`	100.0	0.15	15.00
`code_quality`	57.0	0.10	5.70
Overall		1.00	76.0

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 10 High 120 Medium 48 Low 229 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 183 9-layer 333 Crowd 0 Layer: Quality 182 Security 9 Cicd 54 Software 97 Frontend 118 Network 3 Hardware 3 Api 50

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.

Fragile runtime 120 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

12 matching findings on this repo

medium [MINED111] Bare except continues silently: Bare `except:` (or `except Exception… openapi/generate_openapi.py:811
medium [MINED111] Bare except continues silently: Bare `except:` (or `except Exception… api.py:785
medium [MINED111] Bare except continues silently: Bare `except:` (or `except Exception… api.py:568
medium [MINED111] Bare except continues silently: Bare `except:` (or `except Exception… api.py:412
medium [MINED111] Bare except continues silently: Bare `except:` (or `except Exception… api.py:389
medium robots.txt blocks the full public site public/robots.txt
medium Public web service has no security.txt .well-known/security.txt
medium Public web app has no Content Security Policy index.html
medium Calendar/event date parsing can crash on malformed persisted data models/csvCreator.js:310
medium localStorage write failures are swallowed silently client/components/swimlanes/swimlanes.js:106
medium Calendar/event date parsing can crash on malformed persisted data client/components/gantt/gantt.js:110
medium [ERR002] Empty Catch Block: Empty catch blocks hide errors. server/models/activities.js:313

View all fragile runtime findings →

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 Stray `console.log` in TS/JS — server/routes/legacyAttachments.js:8
low Legacy-named symbol `toLegacy` in packages/wekan-fullcalendar/fullcalendar/full…
low Legacy-named symbol `toLegacy` in packages/wekan-fullcalendar/fullcalendar/full…
low Legacy-named symbol `daysOld` in server/cronJobStorage.js:381
low Legacy-named symbol `daysOld` in server/cronMigrationManager.js:3263

View all legacy markers findings →

Commented-out code 42 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 (5 lines) in api.py:74
info Commented-code block (5 lines) in sandstorm.js:285
info Commented-code block (18 lines) in client/components/settings/settingBody.js:10
info Commented-code block (9 lines) in client/components/lists/listBody.js:692
info Commented-code block (7 lines) in client/components/lists/list.js:98
info Commented-code block (6 lines) in client/components/lib/basicTabs.js:3
info Commented-code block (8 lines) in client/components/swimlanes/swimlanes.js:190
info Commented-code block (9 lines) in client/components/swimlanes/swimlaneHeader.js…
info Commented-code block (10 lines) in client/components/main/popup.js:13
info Commented-code block (6 lines) in client/components/main/editor.js:375
info Commented-code block (5 lines) in client/lib/textComplete.js:60
info Commented-code block (5 lines) in client/lib/utils.js:605

View all commented-out code findings →

Config drift 6 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.

6 matching findings on this repo

high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… packages/wekan-accounts-cas/cas_server.js:63
low File has no detected symbols: rspack.config.js
low File has no detected symbols: client/config/gecko-fix.js
low Stray `console.log` in TS/JS — config/query-classes.js:299
info TODO/FIXME marker in shipping code — config/router.js:564
info Commented-code block (5 lines) in config/router.js:557

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/5937a6d5-bde9-481f-adad-93b0de1062da/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5937a6d5-bde9-481f-adad-93b0de1062da/

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.