Softeria/ms-365-mcp-server

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.

14 of your 43 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.39s · analysis 22.6s · 1.1 MB · GitHub API rate-limit (preflight)

https://github.com/Softeria/ms-365-mcp-server · scanned 2026-06-05 21:54 UTC (1 week, 2 days ago) · 10 languages

143 raw signals (39 security + 104 graph) 73rd percentile · Typescript · small (2-20K LoC) System graph score 64 (higher by 17)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 51 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	72.9	0.25	18.23
`testing_score`	90.0	0.20	18.00
`documentation_score`	64.0	0.15	9.60
`practices_score`	84.0	0.15	12.60
`code_quality`	78.0	0.10	7.80
Overall		1.00	81.2

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 19 Medium 13 Low 43 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 33 System graph 51 Crowd 0 Layer: Quality 17 Security 3 Software 41 Cicd 5 Frontend 7 Hardware 4 Api 7

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

4 matching findings on this repo

info Commented-code block (9 lines) in src/server.ts:238
info Commented-code block (5 lines) in src/graph-tools.ts:579
info Commented-code block (6 lines) in src/audit-log.ts:61
info Commented-code block (5 lines) in src/lib/graph-resilience.ts:260

View all commented-out code findings →

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

3 matching findings on this repo

low File has no detected symbols: vitest.config.js
low File has no detected symbols: tsup.config.ts
low File has no detected symbols: eslint.config.js

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/cf60e75b-602f-4bc7-a210-bb894994b861/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/cf60e75b-602f-4bc7-a210-bb894994b861/

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.