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) 72nd 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: severity: high × 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

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Strongest security (92), testing (85); weakest documentation (48), practices (75).

Showing 18 of 84 actionable findings. 91 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high Security checks software dependencies conf 0.90 ✓ Repobility 2 occurrences Dockerfile FROM `node:24-alpine` not pinned by digest

`FROM node:24-alpine` resolves the tag at build time. The registry CAN re-push a different image for the same tag, so every build is potentially different. Production images should pin to `image@sha256:...` for reproducibility + supply-chain integrity.

lines 1, 11

Dockerfile:1, 11 (2 hits)

high Security checks quality Quality conf 0.80 ✓ Repobility Express POST /mcp has no auth

Express route POST /mcp declared without an auth middleware in its handler chain. Destructive methods (POST/PUT/DELETE/PATCH) on unauthenticated routes are OWASP A01:2021 broken access control.

src/server.ts:660

high Security checks quality Quality conf 0.80 ✓ Repobility Express POST /register has no auth

Express route POST /register declared without an auth middleware in its handler chain. Destructive methods (POST/PUT/DELETE/PATCH) on unauthenticated routes are OWASP A01:2021 broken access control.

src/server.ts:311

high Security checks quality Quality conf 0.80 ✓ Repobility Express POST /token has no auth

Express route POST /token declared without an auth middleware in its handler chain. Destructive methods (POST/PUT/DELETE/PATCH) on unauthenticated routes are OWASP A01:2021 broken access control.

src/server.ts:478

high Security checks software dependencies conf 0.88 picomatch: GHSA-c2c7-rcm5-vvqj

Picomatch has a ReDoS vulnerability via extglob quantifiers

package-lock.json

high System graph api Wiring conf 1.00 Dangling fetch: POST https://graph.microsoft.com/v1.0/me/drive/root:${filePath}:/workbook/createSession (test/graph-api.test.ts:23)

`test/graph-api.test.ts:23` calls `POST https://graph.microsoft.com/v1.0/me/drive/root:${filePath}:/workbook/createSession` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/graph.microsoft.com/v1.0/me/drive/roo…

Dangling fetchFetch

high Security checks security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /token.

A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: POST /token.

src/server.ts:478

high Security checks cicd CI/CD security conf 0.82 Docker final stage has no non-root USER

Docker images run as root unless the image or Dockerfile switches to a non-root user.

Dockerfile:12 CI/CD securitycontainers

high Security checks software dependencies conf 0.90 npm package `@semantic-release/github` is 1 major version(s) behind (11.0.6 -> 12.0.8)

`@semantic-release/github` is pinned/resolved at 11.0.6 but the latest stable release on the npm registry is 12.0.8 (1 major version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PR…

package.json

high Security checks software dependencies conf 0.90 npm package `@toon-format/toon` is 2 major version(s) behind (0.8.0 -> 2.3.0)

`@toon-format/toon` is pinned/resolved at 0.8.0 but the latest stable release on the npm registry is 2.3.0 (2 major version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.

package.json

high Security checks software dependencies conf 0.90 npm package `commander` is 4 major version(s) behind (11.1.0 -> 15.0.0)

`commander` is pinned/resolved at 11.1.0 but the latest stable release on the npm registry is 15.0.0 (4 major version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.

package.json

high Security checks software dependencies conf 0.90 npm package `dotenv` is 1 major version(s) behind (16.4.7 -> 17.4.2)

`dotenv` is pinned/resolved at 16.4.7 but the latest stable release on the npm registry is 17.4.2 (1 major version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.

package.json

high Security checks software dependencies conf 0.90 npm package `globals` is 3 major version(s) behind (14.0.0 -> 17.6.0)

`globals` is pinned/resolved at 14.0.0 but the latest stable release on the npm registry is 17.6.0 (3 major version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.

package.json

high Security checks software dependencies conf 0.90 npm package `open` is 1 major version(s) behind (10.2.0 -> 11.0.0)

`open` is pinned/resolved at 10.2.0 but the latest stable release on the npm registry is 11.0.0 (1 major version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.

package.json

high Security checks software dependencies conf 0.90 npm package `js-yaml` is minor version(s) behind (4.1.1 -> 4.2.0)

`js-yaml` is pinned/resolved at 4.1.1 but the latest stable release on the npm registry is 4.2.0 (minor version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.

package.json

high Security checks software dependencies conf 0.90 npm package `tsx` is minor version(s) behind (4.21.0 -> 4.22.4)

`tsx` is pinned/resolved at 4.21.0 but the latest stable release on the npm registry is 4.22.4 (minor version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.

package.json

high Security checks software dependencies conf 0.90 npm package `prettier` is patch version(s) behind (3.8.1 -> 3.8.3)

`prettier` is pinned/resolved at 3.8.1 but the latest stable release on the npm registry is 3.8.3 (patch version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.

package.json

high Security checks software dependencies conf 0.90 npm package `zod-to-json-schema` is patch version(s) behind (3.25.1 -> 3.25.2)

`zod-to-json-schema` is pinned/resolved at 3.25.1 but the latest stable release on the npm registry is 3.25.2 (patch version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.

package.json

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.