songquanpeng/message-pusher

搭建专属于你的消息推送服务,支持多种消息推送方式,支持 Markdown,基于 Golang 仅单可执行文件,开箱即用

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 53 minutes ago
Added to GitGenius on September 17th, 2026
Created on September 1st, 2020
Open Issues & Pull Requests: 62 (+0)
GitHub issues: Enabled
Number of forks: 529
Total Stargazers: 3,880 (+0)
Total Subscribers: 25 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 23.1 days
Mean response time: 82.1 days
90th percentile: 341.9 days
Tracked items: 14

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

  • enhancement (18)
  • bug (16)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Message-pusher is a message delivery service that enables users to build their own notification platform supporting multiple delivery channels.

The tool solves the problem of sending notifications across different messaging platforms by providing a unified interface. It accepts messages via HTTP requests and routes them to various endpoints including Bark, DingTalk, Discord, email, Feishu, Lark, Telegram, WeChat, and WebSocket. The service supports Markdown formatting in messages and is built as a single executable file written in Go, requiring no external dependencies for deployment.

Developers should choose this tool if they need to consolidate notifications from multiple sources into a single self-hosted service. It suits projects that generate alerts or notifications and want to avoid vendor lock-in by maintaining their own infrastructure. The tool is particularly valuable for teams already using multiple messaging platforms who want a central point to manage and route all outgoing notifications.

The project shows active maintenance with regular updates addressing user feedback and platform compatibility. Development includes ongoing refinement of supported notification channels and database handling. The codebase demonstrates attention to deployment flexibility, offering both standalone executable and Docker container options for different infrastructure preferences.