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.

numpy/numpy

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

273 findings (20 legacy + 253 scanner) 2/10 scanners ran 75th percentile · Python · huge (>500K LoC) Scanner says 99 (lower by 17)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 day, 11 hours ago · v1 · 265 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
{# ── 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: severity: high × excluding tests × Reset all
Severity: Critical 0 High 14 Medium 14 Low 182 Source: Legacy 12 9-layer 253 Crowd 0 Layer: Software 69 Security 16 Quality 177 Api 1 Frontend 1 Cicd 1
Scan summary Repository scanned at 99.2/100 with 88.9% coverage. It contains 13741 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 253 findings — concentrated in quality (173), software (67), security (10). Risk profile is high: 0 critical, 9 high, 7 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

high Legacy security path_traversal conf 0.80 [SEC013] Path Traversal — User Input in File Path: User-controlled input used in file path without sanitization. Allows reading arbitrary files.
Use os.path.realpath() and verify the path starts with your expected base directory. Use secure_filename() for uploads.
numpy/linalg/lapack_lite/clapack_scrub.py:307 path_traversallegacy
high Legacy software file_upload conf 1.00 [SEC032] Unrestricted File Upload — no extension/MIME validation: File upload accepts the user's filename without validating extension, content-type, or magic bytes. Attackers upload `.php`, `.jsp`, or executable files to a web-served directory, then visit the URL to trigger RCE. CWE-434. Examples: Apache Struts (CVE-2017-9805), countless WordPress plugin RCEs.
Validate THREE things server-side: 1. Extension allowlist: ALLOWED = {'.png', '.jpg', '.pdf'} ext = Path(file.filename).suffix.lower() if ext not in ALLOWED: abort(400) 2. Magic-byte check (don't trust the extension): import magic mime = magic.from_buffer(file…
numpy/linalg/lapack_lite/make_lite.py:258 file_uploadlegacy
high 9-layer security owasp conf 1.00 Insecure pattern 'eval_used' in benchmarks/benchmarks/bench_ma.py:141
Found a known-risky pattern (eval_used). Review and replace if possible.
benchmarks/benchmarks/bench_ma.py:141 owaspeval_used
high 9-layer security owasp conf 1.00 Insecure pattern 'eval_used' in numpy/_build_utils/tempita/_tempita.py:320
Found a known-risky pattern (eval_used). Review and replace if possible.
numpy/_build_utils/tempita/_tempita.py:320 owaspeval_used
high 9-layer security owasp conf 1.00 Insecure pattern 'eval_used' in numpy/f2py/auxfuncs.py:632
Found a known-risky pattern (eval_used). Review and replace if possible.
numpy/f2py/auxfuncs.py:632 owaspeval_used
high 9-layer security owasp conf 1.00 Insecure pattern 'eval_used' in numpy/f2py/capi_maps.py:159
Found a known-risky pattern (eval_used). Review and replace if possible.
numpy/f2py/capi_maps.py:159 owaspeval_used
high 9-layer security owasp conf 1.00 Insecure pattern 'exec_used' in benchmarks/benchmarks/bench_indexing.py:29
Found a known-risky pattern (exec_used). Review and replace if possible.
benchmarks/benchmarks/bench_indexing.py:29 owaspexec_used
high 9-layer security owasp conf 1.00 Insecure pattern 'exec_used' in numpy/_build_utils/tempita/_tempita.py:335
Found a known-risky pattern (exec_used). Review and replace if possible.
numpy/_build_utils/tempita/_tempita.py:335 owaspexec_used
high 9-layer security owasp conf 1.00 Insecure pattern 'tls_verify_false' in numpy/_core/multiarray.py:112
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
numpy/_core/multiarray.py:112 owasptls_verify_false
high 9-layer security owasp conf 1.00 Insecure pattern 'tls_verify_false' in numpy/lib/_ufunclike_impl.py:18
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
numpy/lib/_ufunclike_impl.py:18 owasptls_verify_false
high Legacy quality error_handling conf 1.00 [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides bugs. Even in cleanup code, log at DEBUG level.
Log the error: `except Exception: logger.debug('cleanup failed', exc_info=True)`. Or handle specific exception types.
numpy/ma/core.py:1097 error_handlinglegacy
high Legacy quality error_handling conf 1.00 [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides bugs. Even in cleanup code, log at DEBUG level.
Log the error: `except Exception: logger.debug('cleanup failed', exc_info=True)`. Or handle specific exception types.
tools/refguide_check.py:309 error_handlinglegacy
high Legacy quality error_handling conf 1.00 [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides bugs. Even in cleanup code, log at DEBUG level.
Log the error: `except Exception: logger.debug('cleanup failed', exc_info=True)`. Or handle specific exception types.
numpy/_core/function_base.py:486 error_handlinglegacy
{# ── 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/42d62344-be26-4abd-ae9b-1edcf3c5f360/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/42d62344-be26-4abd-ae9b-1edcf3c5f360/

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.