🤖 This is an automated review generated by an AI-powered OSS reviewer bot.
If you'd like to opt out of future reviews, add the label no-bot-review to this repo.
If anything is inaccurate or unhelpful, feel free to close this issue or leave a comment.
Hey @mheidari98! 👋 Thanks for putting this together — free proxy lists are genuinely useful for developers and researchers, and it's great that you're maintaining this publicly. Here are some thoughts!
🌟 Strengths
-
Clean, practical usage instructions — The README gets straight to the point with copy-pasteable commands. The two-step setup (install → run) is easy to follow, and linking to proxyUtil with the exact pip command is a real time-saver for new users. No guessing required!
-
Well-organized categorized links — Breaking the proxy list into all, vmess, and shadowsocks endpoints is a smart design choice. Users who only need a specific protocol don't have to wade through everything, and the raw GitHub URLs make it trivially easy to consume programmatically.
-
Active maintenance — The last push date shows this repo is genuinely kept up to date (even into 2026!), which is the most important quality for a proxy list. A stale list is a useless list, and yours clearly isn't that. 👏
💡 Suggestions
-
Add the missing protocol links to the README — Your topics include trojan and vless, and there's even an open issue specifically requesting Trojan support. It looks like those files may exist (or are planned), but they're not listed in the README's Links section alongside vmess and ss. Adding direct raw URLs for trojan, vless, and any other supported protocols would immediately close that open issue and make the README a single source of truth. Something like:
https://raw.githubusercontent.com/mheidari98/.proxy/main/trojan
https://raw.githubusercontent.com/mheidari98/.proxy/main/vless
-
Add a brief "How proxies are collected" section — The README currently says proxies are "collected from the Internet," which is honest but leaves users wondering about freshness, sources, and update frequency. Even a short paragraph like "This list is automatically updated every 6 hours by scraping public Telegram channels and GitHub repositories" (or whatever the actual mechanism is) would build a lot of trust and help users decide if the list fits their needs. Transparency here also helps distinguish your project from less trustworthy aggregators.
-
Include a disclaimer/legal note about usage — You already have a responsibility disclaimer ("I am not responsible for proxies"), which is good! Consider expanding it slightly to note that users should comply with their local laws and the terms of service of any applications they use these proxies with. This is a small addition that protects both you and your users, and it's increasingly important for projects in this space.
⚡ Quick Wins
-
Add a few README badges — A simple "last updated" or "proxy count" badge at the top would immediately communicate the repo's activity level to visitors. You could auto-generate a badge using shields.io tied to the last commit, e.g.:
-
Pin or close the open "Trojan" issue — Even a quick comment like "Trojan support is tracked at X" or "Added in the latest update — see the trojan file" would show responsiveness to your community and keep your issue tracker clean. 177 stars means people are watching! 🎉
Overall this is a well-structured, genuinely useful project. The improvements above are mostly about making what's already good even more discoverable and trustworthy. Keep up the great work! 🚀
Hey @mheidari98! 👋 Thanks for putting this together — free proxy lists are genuinely useful for developers and researchers, and it's great that you're maintaining this publicly. Here are some thoughts!
🌟 Strengths
Clean, practical usage instructions — The README gets straight to the point with copy-pasteable commands. The two-step setup (install → run) is easy to follow, and linking to
proxyUtilwith the exact pip command is a real time-saver for new users. No guessing required!Well-organized categorized links — Breaking the proxy list into
all,vmess, andshadowsocksendpoints is a smart design choice. Users who only need a specific protocol don't have to wade through everything, and the raw GitHub URLs make it trivially easy to consume programmatically.Active maintenance — The last push date shows this repo is genuinely kept up to date (even into 2026!), which is the most important quality for a proxy list. A stale list is a useless list, and yours clearly isn't that. 👏
💡 Suggestions
Add the missing protocol links to the README — Your topics include
trojanandvless, and there's even an open issue specifically requesting Trojan support. It looks like those files may exist (or are planned), but they're not listed in the README's Links section alongsidevmessandss. Adding direct raw URLs fortrojan,vless, and any other supported protocols would immediately close that open issue and make the README a single source of truth. Something like:Add a brief "How proxies are collected" section — The README currently says proxies are "collected from the Internet," which is honest but leaves users wondering about freshness, sources, and update frequency. Even a short paragraph like "This list is automatically updated every 6 hours by scraping public Telegram channels and GitHub repositories" (or whatever the actual mechanism is) would build a lot of trust and help users decide if the list fits their needs. Transparency here also helps distinguish your project from less trustworthy aggregators.
Include a disclaimer/legal note about usage — You already have a responsibility disclaimer ("I am not responsible for proxies"), which is good! Consider expanding it slightly to note that users should comply with their local laws and the terms of service of any applications they use these proxies with. This is a small addition that protects both you and your users, and it's increasingly important for projects in this space.
⚡ Quick Wins
Add a few README badges — A simple "last updated" or "proxy count" badge at the top would immediately communicate the repo's activity level to visitors. You could auto-generate a badge using shields.io tied to the last commit, e.g.:
Pin or close the open "Trojan" issue — Even a quick comment like "Trojan support is tracked at X" or "Added in the latest update — see the
trojanfile" would show responsiveness to your community and keep your issue tracker clean. 177 stars means people are watching! 🎉Overall this is a well-structured, genuinely useful project. The improvements above are mostly about making what's already good even more discoverable and trustworthy. Keep up the great work! 🚀