fortra/impacket

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/fortra/impacket · scanned 2026-05-15 16:00 UTC (3 weeks ago) · 10 languages

276 findings (32 legacy + 244 scanner) 58th percentile · Python · large (100-500K LoC) Scanner says 64 (higher by 13)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 3 weeks ago · v1 · 21 findings from 1 source. 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-14-v3

Component	Sub-score	Weight	Contribution
`structure_score`	75.0	0.15	11.25
`security_score`	79.5	0.25	19.88
`testing_score`	100.0	0.20	20.00
`documentation_score`	72.0	0.15	10.80
`practices_score`	75.0	0.15	11.25
`code_quality`	43.1	0.10	4.31
Overall		1.00	77.5

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 8 Medium 12 Low 0 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 21 9-layer 0 Crowd 0 Layer: Quality 9 Security 8 Cicd 4

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Fragile runtime 9 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

9 matching findings on this repo

medium Public web service has no security.txt .well-known/security.txt
medium [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides … impacket/smb3.py:712
medium [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides … impacket/smbserver.py:4387
medium [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides … impacket/tds.py:1561
medium Duplicated implementation block across source files impacket/mqtt.py:159
medium Duplicated implementation block across source files impacket/krb5/keytab.py:80
medium Duplicated implementation block across source files impacket/dcerpc/v5/tsch.py:23
medium Duplicated implementation block across source files impacket/dcerpc/v5/rprn.py:7
medium Average file size is 560 lines (recommend <300)

View all fragile runtime findings →

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/9034f894-6baa-4d67-938c-5b1fd00c9965/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9034f894-6baa-4d67-938c-5b1fd00c9965/

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.