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

Scan timing: clone 2.66s · analysis 13.98s · 2.4 MB · GitHub API rate-limit (preflight)

Meeting-BaaS/meet-teams-bot

https://github.com/Meeting-BaaS/meet-teams-bot · scanned 2026-06-05 13:25 UTC (5 days, 7 hours ago) · 10 languages

307 raw signals (123 security + 184 graph) 33rd percentile · Typescript · small (2-20K LoC)

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

Complete repo analysis

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

JSON
Combined
64.2
/100
Security checks
68
111 findings
System graph
61
100.0% cov · 92 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 100.0 0.15 15.00
security_score 42.8 0.25 10.70
testing_score 27.0 0.20 5.40
documentation_score 90.0 0.15 13.50
practices_score 62.0 0.15 9.30
code_quality 69.4 0.10 6.94
Overall 1.00 60.8
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 4 High 41 Medium 41 Low 86 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 111 System graph 92 Crowd 0 Layer: Quality 34 Security 5 Software 93 Cicd 7 Frontend 52 Hardware 4 Api 8

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

#1
Possible secret in src/main.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 src/main.ts:223; move to env var / secrets manager.
src/main.ts:223
#2
Dockerfile pipes a remote installer into a shell
GapSeverity.HIGH Layer.HARDWARE score 0.375
Why: high severity
Dockerfile:6
#3
Dangling fetch: POST /bots/end_meeting_trampoline (src/api/methods.ts:79)
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.
#4
Dangling fetch: POST /bots/transcripts/${GLOBAL.get().bot_uuid}/diarization (src/api/methods.ts:99)
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.
#5
Dangling fetch: PATCH /bots/transcripts/${GLOBAL.get().bot_uuid}/diarization (src/api/methods.ts:112)
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.
#6
Dangling fetch: POST /bots/start_record_failed (src/api/methods.ts:133)
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.
#7
Dangling fetch: GET /bots/check_stop_request (src/api/methods.ts:159)
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.
#8
Dockerfile runs as root: Dockerfile
GapSeverity.MEDIUM Layer.HARDWARE score 0.225
Why: medium severity
#9
No CI/CD pipelines detected
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
#10
Very low test-to-source ratio
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity

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/93651174-a399-4865-826f-fab6ccfec7c5/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/93651174-a399-4865-826f-fab6ccfec7c5/

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.