Meeting-BaaS/meet-teams-bot

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.

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)

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

100.0% cov · 92 findings

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

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.

Commented-out code 11 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/`.

11 matching findings on this repo

info Commented-code block (5 lines) in src/media_context.ts:179
info Commented-code block (5 lines) in src/types.ts:21
info Commented-code block (5 lines) in src/recording/ScreenRecorder.ts:224
info Commented-code block (5 lines) in src/utils/S3Uploader.ts:15
info Commented-code block (5 lines) in src/proxy/toggle-proxy.ts:2
info Commented-code block (5 lines) in src/meeting/meet.ts:44
info Commented-code block (6 lines) in src/meeting/teams.ts:70
info Commented-code block (6 lines) in src/meeting/teams/htmlCleaner.ts:51
info Commented-code block (6 lines) in src/state-machine/constants.ts:14
info Commented-code block (5 lines) in src/state-machine/states/waiting-room-state.t…
info Commented-code block (6 lines) in src/state-machine/states/initialization-state…

View all commented-out code findings →

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

5 matching findings on this repo

medium No CI/CD configuration found
low @smithy/config-resolver: GHSA-6475-r3vj-m8vf package-lock.json
low File has no detected symbols: jest.config.js
low File has no detected symbols: src/meeting/meet-state-config.ts
low File has no detected symbols: src/meeting/teams-state-config.ts

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/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.