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

dotnet/aspnetcore

https://github.com/dotnet/aspnetcore.git · scanned 2026-05-16 12:51 UTC (1 day, 8 hours ago) · 10 languages

396 findings (15 legacy + 381 scanner) 2/10 scanners ran Scanner says 76 (higher by 12)

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

Complete repo analysis

Last scanned 1 day, 10 hours ago · v3 · 132 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
83.6
/100
Repobility
91
5 legacy
9-layer
76
100.0% cov · 127 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
{# ── 2026-05-17 R27 #5: score breakdown panel ────────────────────── Surfaces the score_breakdown JSON that's been silently stored on Repository for months. Turns hidden math into a trust signal. #}
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 4 Medium 27 Low 73 Source: Legacy 5 9-layer 127 Crowd 0 Layer: Security 2 Software 54 Frontend 22 Network 3 Hardware 3 Cicd 10 Quality 38

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

#1
Privileged port 16 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in .github/workflows/labeler-cache-retention.yml is a real port, change the binding to ≥1024 or run behind a proxy.
.github/workflows/labeler-cache-retention.yml
#2
Privileged port 32 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in .github/workflows/labeler-cache-retention.yml is a real port, change the binding to ≥1024 or run behind a proxy.
.github/workflows/labeler-cache-retention.yml
#3
Privileged port 13 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in .github/workflows/backport.yml is a real port, change the binding to ≥1024 or run behind a proxy.
.github/workflows/backport.yml
#4
Insecure pattern 'subprocess_shell_true' in eng/common/cross/install-debs.py:236
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
eng/common/cross/install-debs.py:236
#5
Docker base image uses a mutable or implicit tag: mcr.microsoft.com/devcontainers/dotnet:latest
GapSeverity.MEDIUM Layer.HARDWARE score 0.225
Why: medium severity
.devcontainer/Dockerfile:2
#6
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/inter-branch-merge-flow.yml
#7
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/browsertesting-deps-update.lock.yml
#8
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/runtime-sync.yml
#9
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/cswin32-update.lock.yml
#10
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/update-sdk.yml

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.

{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}
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/0cb66c23-9b5d-42ea-ac89-f6a9798820ee/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/0cb66c23-9b5d-42ea-ac89-f6a9798820ee/

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.