router-for-me/cli-proxy-api-management-center

This is a WebUI interface based on CLI-Proxy-API, designed to simplify configuration modifications and runtime status monitoring.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 52 minutes ago
Added to GitGenius on September 16th, 2026
Created on September 6th, 2025
Open Issues & Pull Requests: 24 (+0)
GitHub issues: Enabled
Number of forks: 1,273
Total Stargazers: 4,282 (+0)
Total Subscribers: 7 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 25.5 hours
Mean response time: 2.6 days
90th percentile: 6.1 days
Tracked items: 197

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Practically every issue opened in the past year has drawn a reply. 94% of issues opened in the past year have since been closed. Three people close 86% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 12
New in 7 days: 10
Closed in 7 days: 5
Avg open age: 17 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 9
Closed in 7 days: 4
Comments in 7 days: 7
Events in 7 days: 14

Top labels

  • codex (2)
  • enhancement (2)
  • lampoon (1)
  • question (1)

Detailed Description

CLI-Proxy-API-Management-Center is a web-based management interface for proxy configuration and monitoring.

The tool addresses the complexity of managing proxy configurations and observing runtime behavior through a graphical interface. It builds on top of CLI-Proxy-API, translating command-line operations into a web UI that allows operators to modify settings and track system status without direct terminal access. This approach makes proxy management more accessible to users who prefer graphical workflows over command-line interaction.

The project suits teams that need centralized visibility into proxy operations and want to reduce friction in configuration changes. It is particularly valuable in environments where multiple operators need to adjust proxy settings or where audit trails and UI-driven workflows are preferred over scripting. Anyone considering adoption should verify that their existing CLI-Proxy-API setup is compatible and that the web interface covers the specific configuration and monitoring tasks their deployment requires.

The project shows active development with regular commits across multiple areas of the codebase. Work spans both core functionality and infrastructure, with attention to maintaining the TypeScript implementation and updating dependencies. The maintainers respond to issues and incorporate feedback into the tool.