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
Upstream (GitHub) caused delay on this scan — not Repobility.
  • Clone from GitHub took 73.41s for a 138.1 MB repo slow.
  • Repobility's analysis ran in 24.4s after the clone landed.

13145125121/BotTG

https://github.com/13145125121/BotTG.git · scanned 2026-05-28 22:10 UTC (1 week ago) · 10 languages

2021 findings (206 legacy + 1815 scanner) 10/13 scanners ran 68th percentile · Typescript · large (100-500K LoC) Scanner says 59 (higher by 20)

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

Complete repo analysis

Last scanned 1 week ago · v3 · 811 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
Combined
73.7
/100
Repobility
88
206 legacy
9-layer
59
100.0% cov · 605 gaps
Critical
13
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 44.0 0.20 8.80
documentation_score 87.0 0.15 13.05
practices_score 94.0 0.15 14.10
code_quality 60.0 0.10 6.00
Overall 1.00 79.7
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 13 High 116 Medium 93 Low 435 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 206 9-layer 605 Crowd 0 Layer: Quality 264 Security 60 Cicd 9 Software 65 Frontend 354 Hardware 4 Api 55

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in scripts/force-push.sh
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in scripts/force-push.sh:38; move to env var / secrets manager.
scripts/force-push.sh:38
#2
Possible secret in scripts/fix_texts_encoding.py
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in scripts/fix_texts_encoding.py:18; move to env var / secrets manager.
scripts/fix_texts_encoding.py:18
#3
Possible secret in server/telegram/services/auth/qr-2fa-verifier.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in server/telegram/services/auth/qr-2fa-verifier.ts:43; move to env var / secrets manager.
server/telegram/services/auth/qr-2fa-verifier.ts:43
#4
Possible secret in server/telegram/services/auth/qr-2fa-verifier.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in server/telegram/services/auth/qr-2fa-verifier.ts:59; move to env var / secrets manager.
server/telegram/services/auth/qr-2fa-verifier.ts:59
#5
Possible secret in server/routes/routes.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in server/routes/routes.ts:4266; move to env var / secrets manager.
server/routes/routes.ts:4266
#6
Insecure pattern 'exec_used' in server/python/worker.py:225
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
server/python/worker.py:225
#7
`dangerouslySetInnerHTML` used in a React component — client/components/ui/chart.tsx:81
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#8
`dangerouslySetInnerHTML` used in a React component — client/components/editor/inline-rich/components/FormattedText.tsx:3
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#9
Dangling fetch: GET https://api.telegram.org/bot${token}/getMe (client/components/editor/bot/token/tokenUtils.ts:25)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#10
Dangling fetch: GET /api/projects/${projectId}/telegram-client/group-members/${selectedGroup.groupId} (client/components/editor/groups/groups-panel.tsx:3509)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/82a13e96-2f14-4509-b156-00a97ca752ff/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/82a13e96-2f14-4509-b156-00a97ca752ff/

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.