nikoksr/notify

A dead simple Go library for sending notifications to various messaging services.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 59 minutes ago
Added to GitGenius on September 17th, 2026
Created on January 24th, 2021
Open Issues & Pull Requests: 44 (+0)
GitHub issues: Enabled
Number of forks: 293
Total Stargazers: 3,878 (+0)
Total Subscribers: 18 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 40.5 days
Mean response time: 151.8 days
90th percentile: 346.4 days
Tracked items: 23

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 24
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,275 days
Stale 30+ days: 23
Stale 90+ days: 22

Recent activity

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

Top labels

  • area/services (18)
  • help wanted (18)
  • good first issue (17)
  • type/enhancement (17)
  • area/core (1)
  • status/needs-info (1)
  • type/bug (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Notify is a Go library for sending notifications to various messaging services.

The library solves the problem of integrating multiple notification platforms into a single application. Rather than writing separate code for each service, developers can use a unified interface to send messages across different channels. The tool supports numerous messaging platforms including Slack, Discord, Telegram, Microsoft Teams, Twilio, SendGrid, AWS SES, Twitter, WeChat, WhatsApp, Rocket.Chat, and PushBullet. It provides both global convenience functions similar to logging libraries and local constructor functions for creating dedicated Notify instances that can be passed through an application.

The library is suited for applications that need to notify users or administrators across multiple channels without managing separate integrations for each platform. It works well for alert systems, user notifications, and multi-channel messaging scenarios. The README explicitly recommends avoiding global functions in favor of creating local instances and passing them through the application, suggesting this pattern is important for maintainability in larger codebases. The project acknowledges that it depends on the consistency of external services and their client libraries, and therefore should not be used in critical scenarios where reliability is essential. The README also warns that misuse could result in permanent bans on supported platforms.

The project actively solicits contributions and maintains a list of missing services awaiting implementation. The maintainers encourage both general contributions and specifically invite developers to add new service integrations, indicating an open approach to expanding the library's capabilities through community effort.