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.
32 of your 92 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

huggingface/accelerate

https://github.com/huggingface/accelerate.git · scanned 2026-05-18 14:47 UTC (2 weeks, 3 days ago) · 10 languages

644 findings (92 legacy + 552 scanner) 63rd percentile · Python · medium (20-100K LoC) Scanner says 77 (lower by 10)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks, 3 days ago · v3 · 248 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
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 34.0 0.25 8.50
testing_score 90.0 0.20 18.00
documentation_score 90.0 0.15 13.50
practices_score 72.0 0.15 10.80
code_quality 36.0 0.10 3.60
Overall 1.00 67.1
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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

#1
Insecure pattern 'eval_used' in benchmarks/fp8/torchao/fp8_utils.py:106
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
benchmarks/fp8/torchao/fp8_utils.py:106
#2
Insecure pattern 'eval_used' in benchmarks/fp8/torchao/fsdp.py:56
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
benchmarks/fp8/torchao/fsdp.py:56
#3
Insecure pattern 'eval_used' in benchmarks/fp8/torchao/ddp.py:39
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
benchmarks/fp8/torchao/ddp.py:39
#4
Insecure pattern 'eval_used' in benchmarks/fp8/torchao/non_distributed.py:38
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
benchmarks/fp8/torchao/non_distributed.py:38
#5
Insecure pattern 'eval_used' in benchmarks/fp8/transformer_engine/fp8_utils.py:106
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
benchmarks/fp8/transformer_engine/fp8_utils.py:106
#6
Insecure pattern 'eval_used' in benchmarks/fp8/ms_amp/fp8_utils.py:106
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
benchmarks/fp8/ms_amp/fp8_utils.py:106
#7
Insecure pattern 'eval_used' in benchmarks/torch.compile/regional_compilation.py:49
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
benchmarks/torch.compile/regional_compilation.py:49
#8
Privileged port 59 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in examples/slurm/submit_multigpu.sh is a real port, change the binding to ≥1024 or run behind a proxy.
examples/slurm/submit_multigpu.sh
#9
No auth library detected
GapSeverity.MEDIUM Layer.SECURITY score 0.338
Why: medium severity
#10
Docker base image uses a mutable or implicit tag: continuumio/miniconda3:latest
GapSeverity.MEDIUM Layer.HARDWARE score 0.225
Why: medium severity
docker/accelerate-gpu-deepspeed/Dockerfile:5

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.

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/997bbbe3-2683-4e32-a73e-484d75ceba8d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/997bbbe3-2683-4e32-a73e-484d75ceba8d/

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.