Barabama/FreeNodes

v2ray、clash免费节点爬虫,自动更新

View on GitHub ↗Jump to charts ↓

Barabama/FreeNodes has 3k+ stars and 400+ forks on GitHub, is written in Python, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 10 minutes ago
Added to GitGenius on September 21st, 2026
Created on July 30th, 2023
Open Issues & Pull Requests: 3 (+0)
GitHub issues: Enabled
Number of forks: 402
Total Stargazers: 3,289 (+0)
Total Subscribers: 45 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 78.0 days
Mean response time: 144.3 days
90th percentile: 392.0 days
Tracked items: 15

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 7 days
Stale 30+ days: 1
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • invalid (8)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Freenodes is a web scraper that automatically collects and updates free proxy nodes for v2ray and clash proxy tools.

The tool addresses the need to maintain current lists of free proxy nodes by crawling various sources and automatically refreshing the collected data. It supports multiple proxy protocols including Shadowsocks, Trojan, VLESS, and VMESS, making the collected nodes compatible with both v2ray and clash clients. The scraper handles the repetitive task of finding working nodes across different sources and keeping them current without manual intervention.

This tool suits users who need access to free proxy nodes for v2ray or clash and want an automated solution rather than manually searching for and validating nodes. It is most appropriate for those comfortable running a Python-based scraper and managing the collected node lists. The project focuses specifically on free node collection with automatic updates, distinguishing it from manual node list maintenance.

The project shows active development with regular commits addressing bug fixes and feature improvements. The codebase demonstrates ongoing refinement of the scraping logic and node validation mechanisms. Updates appear driven by the practical need to maintain compatibility as proxy services and node availability change over time.