Source: https://seerepo.com/r/jhao104/proxy_pool
Markdown source: https://seerepo.com/r/jhao104/proxy_pool.md
Description: jhao104/proxy_pool is a Python repo with 5,508 lines written. proxy_pool is built with Flask and werkzeug and uses Redis.

# What's inside jhao104/proxy_pool

jhao104/proxy_pool is a Python repo with 5,508 lines written. proxy_pool is built with Flask and werkzeug and uses Redis.

Its description on GitHub: “Python ProxyPool for web spider”

Python · MIT · 23,781 stars · GitHub: https://github.com/jhao104/proxy_pool

Read on November 4, 2026, at commit 9cc0cad.

## More on this repo

- [What is proxy_pool built with?](https://seerepo.com/r/jhao104/proxy_pool/built): proxy_pool is built with Flask and werkzeug and uses Redis.
- [How much of proxy_pool did AI write?](https://seerepo.com/r/jhao104/proxy_pool/ai): No AI tool signed any of the 533 commits of proxy_pool.

## In figures

- 5,508 lines written: The ones people and agents wrote: product, tests, schemas and tooling. Generated code doesn’t count.
- 40 files: The product’s, not counting tests.
- 22 test files: The files that test the code.
- 5 technologies: Each service with the file and line that prove it.

SeeRepo read the facts in its code and kept none of it. AI only helps sort its packages and folders by their names, and never sees its code.

## Frequently asked questions

### What is jhao104/proxy_pool?

jhao104/proxy_pool is a Python repo with 5,508 lines written. Its description on GitHub: “Python ProxyPool for web spider”

The proof: [its page on GitHub](https://github.com/jhao104/proxy_pool)

### What is proxy_pool built with?

proxy_pool is built with Flask and werkzeug and uses Redis.

The proof: [each service with its file and line](https://seerepo.com/r/jhao104/proxy_pool/built)

### What license does proxy_pool have?

proxy_pool is released under the MIT license.

The proof: [its page on GitHub](https://github.com/jhao104/proxy_pool)

### How many stars does proxy_pool have on GitHub?

proxy_pool had 23,781 stars on GitHub on November 4, 2026.

The proof: [its page on GitHub](https://github.com/jhao104/proxy_pool)

## Add this badge to your README

It links to this page and updates itself each time SeeRepo reads the repo.

```markdown
[![jhao104/proxy_pool on SeeRepo](https://seerepo.com/badge/jhao104/proxy_pool.svg)](https://seerepo.com/r/jhao104/proxy_pool?de=insignia)
```

## What is your repo built with?

Any public repo, with no account: https://seerepo.com/r/owner/repo/built, with the owner and name it has on GitHub.
