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

erxes/erxes

https://github.com/erxes/erxes · scanned 2026-05-31 01:22 UTC (1 week, 6 days ago) · 10 languages

1978 raw signals (93 security + 1885 graph) 11/13 scanners ran 26th percentile · Typescript · medium (20-100K LoC) System graph score 51 (higher by 9)

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

Complete repo analysis

Last scanned 1 week, 6 days ago · v2 · last Δ -0.2 (diff) · 641 actionable findings from 2 signal sources. 403 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
62.1
/100
Security checks
73
27 findings
System graph
51
100.0% cov · 614 findings
Critical
4
click to filter
Agents
6
0 votes
Crowd
0
reported
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 0.0 0.20 0.00
documentation_score 60.0 0.15 9.00
practices_score 61.0 0.15 9.15
code_quality 80.0 0.10 8.00
Overall 1.00 60.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 4 High 14 Medium 119 Low 253 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 27 System graph 614 Crowd 0 Layer: Quality 197 Security 29 Cicd 4 Software 51 Frontend 285 Network 1 Hardware 12 Api 62

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 2 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.
2 matching findings on this repo
  • low Old/deprecated-named symbol `ActivityLogsLegacy` in frontend/libs/ui-modules/sr…
  • low Old/deprecated-named symbol `SegmentFormLegacy` in frontend/libs/ui-modules/src…
View all legacy markers findings →
Commented-out code 89 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 (8 lines) in frontend/libs/ui-modules/src/modules/products…
  • info Commented-code block (7 lines) in frontend/libs/ui-modules/src/modules/segments…
  • info Commented-code block (8 lines) in frontend/libs/erxes-ui/src/constants/EmailVal…
  • info Commented-code block (8 lines) in frontend/libs/erxes-ui/src/constants/PhoneVal…
  • info Commented-code block (7 lines) in frontend/core-ui/src/modules/settings/securit…
  • info Commented-code block (6 lines) in frontend/core-ui/src/modules/settings/structu…
  • info Commented-code block (8 lines) in frontend/core-ui/src/modules/settings/team-me…
  • info Commented-code block (5 lines) in frontend/core-ui/src/modules/settings/team-me…
  • info Commented-code block (7 lines) in frontend/core-ui/src/modules/templates/compon…
  • info Commented-code block (6 lines) in frontend/core-ui/src/modules/products/product…
  • info Commented-code block (5 lines) in frontend/plugins/content_ui/src/modules/cms/s…
  • info Commented-code block (5 lines) in frontend/plugins/content_ui/src/modules/cms/p…
View all commented-out code findings →
Config drift 16 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
  • low File has no detected symbols: jest.config.ts
  • low File has no detected symbols: eslint.config.js
  • low File has no detected symbols: frontend/libs/ui-modules/jest.config.ts
  • low File has no detected symbols: frontend/libs/ui-modules/eslint.config.js
  • low File has no detected symbols: frontend/libs/ui-modules/src/states/pluginsConfig…
  • low File has no detected symbols: frontend/libs/ui-modules/src/states/clientConfigA…
  • info `truncate` class without `title=` for hover reveal — frontend/plugins/loyalty_u…
  • info `truncate` class without `title=` for hover reveal — frontend/plugins/mongolian…
  • low Stray `console.log` in TS/JS — backend/plugins/posclient_api/src/configMiddlewa…
  • low Stray `console.log` in TS/JS — backend/plugins/posclient_api/src/modules/poscli…
  • low Stray `console.log` in TS/JS — backend/plugins/mongolian_api/src/commands/CoreC…
  • info TODO/FIXME marker in shipping code — backend/plugins/accounting_api/src/modules…
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/b925c108-67c6-44cc-b208-3b57b7f7314c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/b925c108-67c6-44cc-b208-3b57b7f7314c/

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.