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: layer: hardware × 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
Scan summary Repository scanned at 76.1/100 with 100.0% coverage. It contains 15739 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 127 findings — concentrated in software (50), quality (38), frontend (22). Risk profile is low: 0 critical, 0 high, 26 medium. Recommended next step: open the software layer findings first — that's where the highest-impact wins live.

Showing 3 of 132 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium 9-layer hardware supply-chain conf 1.00 Docker base image uses a mutable or implicit tag: mcr.microsoft.com/devcontainers/dotnet:latest
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
.devcontainer/Dockerfile:2 supply-chaindockerpinned-dependencies
medium 9-layer hardware security conf 1.00 Dockerfile runs as root: .devcontainer/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
securitycontainer
low 9-layer hardware coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
coveragedeployment
{# ── 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.