hafrey1/lunatv-config

MoonTV/LunaTV源配置,每日自动检测API状态,可在CF部署CORSAPI中转被墙API,本人提供的CORSAPI仅为测试使用,请勿滥用!

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 19 minutes ago
Added to GitGenius on September 16th, 2026
Created on June 5th, 2025
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 1,603
Total Stargazers: 4,210 (+0)
Total Subscribers: 34 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 30.5 hours
Mean response time: 2.1 days
90th percentile: 4.8 days
Tracked items: 23

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
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

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

LunaTV-config is a configuration repository for MoonTV and LunaTV source management that automates API status monitoring and provides CORS proxy capabilities.

The tool addresses the problem of maintaining reliable video source configurations by performing daily automated checks on API availability. It enables deployment of a CORS API proxy on Cloudflare to forward requests to blocked or restricted APIs, allowing continued access to video sources that might otherwise be unavailable due to network restrictions or geographic blocking.

This project suits developers working with MoonTV or LunaTV implementations who need to maintain stable source configurations and handle API accessibility issues. The automated daily status detection reduces manual maintenance overhead by continuously verifying which sources remain functional. The CORS proxy deployment option provides a workaround for API access restrictions, though the README notes that the provided CORS API is intended for testing purposes only and should not be abused.

The project shows active maintenance with regular updates to source configurations and API status checks. Development activity demonstrates ongoing attention to keeping the source list current and functional as APIs change or become unavailable.