curl/curl

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.

https://github.com/curl/curl.git · scanned 2026-05-16 13:30 UTC (1 day, 4 hours ago) · 10 languages

119 findings (11 legacy + 108 scanner) 8/10 scanners ran Scanner says 93 (lower by 34)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 day, 8 hours ago · v2 · 64 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

Severity distribution — click a segment to filter

Active filters: severity: medium × excluding tests × Reset all

Scan summary Repository scanned at 93.4/100 with 88.9% coverage. It contains 3030 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 54 findings — concentrated in quality (47), network (2), api (1). Risk profile is high: 0 critical, 1 high, 3 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

medium Legacy quality practices conf 1.00 [CFG006] Missing .gitignore: No .gitignore file. Risk of committing secrets and build artifacts.

Add a .gitignore appropriate for your language/framework.

practiceslegacy

medium Legacy cicd docker conf 0.90 Docker build context has no .dockerignore

Add .dockerignore with at least .git, .env, private keys, dependency folders, build outputs, and local databases.

.dockerignore dockerlegacy

medium 9-layer security coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). Either auth lives in custom code, in a separate service, or is missing.

coverageauth

medium 9-layer network security conf 1.00 Privileged port 256 in use

Port 256 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

Dockerfile securityports

medium 9-layer network security conf 1.00 Privileged port 67 in use

Port 67 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

Dockerfile securityports

{# ── 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/8f98161c-b05e-4334-8527-5acaa3d0da82/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/8f98161c-b05e-4334-8527-5acaa3d0da82/

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.