// readme

简体中文 | English

概览

蓝鲸 API 网关（API Gateway），是一种高性能、高可用的 API 托管服务，可以帮助开发者创建、发布、维护、监控和保护 API， 以快速、低成本、低风险地对外开放蓝鲸应用或其他系统的数据或服务。

蓝鲸 API 网关分为控制面和数据面，控制面负责 API 的配置、发布、监控、权限管理等功能，数据面负责 API 的流量转发、安全防护等功能。其中数据面是基于 Apache APISIX 增加一系列插件以支持蓝鲸 API 网关的特性。得益于 Apache APISIX 动态、实时、高性能等特点，蓝鲸 API 网关能够支持高并发、低延迟的 API 托管服务。

本项目是 蓝鲸 API 网关 - 控制面。

蓝鲸 API 网关核心服务开源项目

  • 蓝鲸 API 网关 - 控制面
    • dashboard：API 网关的控制面
    • dashboard-front: API 网关控制面前端
    • operator: 网关配置转换
    • core-api: 网关高性能核心 API
    • mcp-proxy: 网关 MCP server 代理
    • esb: ESB 组件服务
  • 蓝鲸 API 网关 - 数据面

功能特性

  • API 生命周期管理: 涵盖 API 的配置、发布、测试、监控、下线等各个生命周期的管理。
  • 版本发布: 支持多环境管理，用户可新建环境，满足开发、测试、正式等多环境的需求;提供 API 的版本管理，各环境可一键切换版本，互不影响。
  • 文档和SDK: 提供在线文档，及调用网关 API 的 SDK，降低 API 的使用门槛。
  • 权限管理: 默认开启权限限制, 支持权限期限及授权维度。
  • 安全防护: 支持蓝鲸应用认证、用户认证，控制请求来源; 支持 IP 访问控制，可设置 IP 黑/白名单; 支持秒级的流量控制，可根据需求进行流量分配，以避免高流量导致的后端服务过载; 支持操作审计。
  • 可观测性: 支持调用流水查询; 支持接入 OpenTelemetry; 内置多种告警策略。

快速开始

支持

  • [蓝鲸 API…
↑ The Undervalued Score +

How much a project earns versus how much attention it actually gets. Above 50 means the work is outrunning its audience. Recomputed nightly from commit velocity, contributor effort, issue resolution, fork utility, release cadence, and project maturity — divided by a logarithmic reach factor.

score  = signal / reach

signal = 0.25·commit_velocity   // commits in last 90 days (cap 30)
       + 0.20·contributor_work  // unique authors × velocity (cap 100)
       + 0.20·issue_resolution  // closed ÷ total issues
       + 0.20·fork_ratio        // forks ÷ stars (proxy for real usage)
       + 0.10·release_cadence   // releases in 90 days (cap 3)
       + age_bonus              // +0 to +0.30 after 6 months
       + homepage_bonus         // +0.05 if homepage is set

reach  = log₁₀(stars + watchers + 10)█
♥ The Health Score +

Is the project alive and maintained right now? A 0–100 pulse recomputed nightly from commit recency, rhythm, how fast issues close, and how quickly PRs get merged.

health = 0.35·recency       // days since last commit (90d decay)
       + 0.25·cadence       // commit rhythm consistency
       + 0.20·issue_health  // closed ÷ total issues
       + 0.20·pr_health     // merged ÷ total PRs█
◷ Health bands +

The colour and label on every card come straight from the health score.

Healthy   80 – 100   active, responsive, regular releases
Stable    60 – 79    maintained, steady, no alarms
Quiet     40 – 59    slowing down — watch this one
At Risk    0 – 39    going dark · candidate for rescue█
// Tags — what each label means +

Tags are independent behavioral signals computed nightly. A project can hold multiple at once. They drive the home page sections.

solo_builder      one person holds > 80% of commits (last 180d)
needs_contributors has open "help wanted" or "good first issue" labels
hidden_gem        < 100 stars · active in last 3 months · documented
legacy_hero       repo > 5 years old · committed this year
fork_magnet       forks/stars > 0.5 · used as template or dependency
release_machine   5+ releases in the last 90 days
under_pressure    > 10 open issues · ≤ 2 contributors · health ≥ 60
community_watch   watchers > stars · devs tracking before the public
community_hub     GitHub Discussions enabled · > 20 discussions
funded            maintainer has active funding channel█
★ Why rank against stars at all? +

Stars are an outcome, not effort. A project with 8 stars and daily commits is doing more interesting work than one coasting on 8k. We measure the building, then divide by the attention already received — so the genuinely undervalued rise to the top.

// stars   = lagging indicator
// commits = leading indicator
// we rank by the leading one█