freeproxy
FreeProxy: Collecting free proxies from internet. (全球海量高质量免费代理,支持爬取数十个免费代理分享源,支持自定义规则代理筛选,爬虫与数据分析必备,每日更新海量免费代理。)
Runssource: GitHubhomepagePythonApache-2.0commit a32e93087029
Python, Apache-2.0 licensed. The project labels itself: 996icu, crawler, icu, iplocation, iplocator, proxy, proxy checker and proxy server.
freeproxy runs. An Argusic agent installed it in 12 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
pyfreeproxy v0.5.2 installed in /tmp/venv, all 48 proxy sources registered, Proxifly/ProxyScrape/Geonode scrape real proxies successfully, filter rules and ProxiedSessionClient work, JSON export round-trips correctly, free proxies collected but actual proxy requests time out as expected from this container network
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- externally-managed-environment pip error on Debian2 minutes
- 'python' binary not found; only python3 available0.5 minutes
- Missing SOCKS support for proxy protocol0.5 minutes
- Install time
- 12 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pip install -e . in venv succeeded; 'python -c "from freeproxy.modules import ProxiedSessionBuilder; print(len(ProxiedSessionBuilder.REGISTERED_MODULES))"' returned 48; 'ProxiflyProxiedSession.refreshproxies()' returned 74928 proxies; 'ProxyScrapeProxiedSession.refreshproxies()' returned 1000 proxies; 'GeonodeProxiedSession.refreshproxies()' returned 500 proxies; filter_rule reduced 74928 to 7012; JSON save/load validated
- Model tokens used
- 131,856
- Exact commit tested
- a32e93087029
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- PySocks needed for SOCKS proxy format (installed) tokens used 131,856 Here's the final summary of all findings: **Installation**: ✅ Created venv, installed all dependencies, built and installed `pyfreeproxy` 0.5… **Core functionality verified**: - Library imports correctly, 48 proxy sources registered - Proxy scraping from multiple real sources (Proxifly: ~75K, ProxyScrape: 1K, Geonode: 500) - Filter rules work (74,928 → 7,012 for http/https) - `ProxiedSessionClient` unified client initializes and pools proxies - JSON save/load round-trip tested - PySocks needed for SOCKS proxy format (installed)
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 12 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
996icucrawlericuiplocationiplocatorproxyproxy-checkerproxy-serverproxy-sourcesproxypoolrequestsspider
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/freeproxy)Questions
- Does freeproxy run?
- Yes. freeproxy runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test freeproxy?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a32e93087029. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test freeproxy?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does freeproxy take to install?
- 12 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does freeproxy need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing freeproxy?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for freeproxy?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.