sendgrid/sendgrid-nodejs

The Official Twilio SendGrid Led, Community Driven Node.js API Library

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 22nd, 2026
Created on January 6th, 2012
Open Issues & Pull Requests: 101 (+0)
GitHub issues: Enabled
Number of forks: 781
Total Stargazers: 3,052 (+0)
Total Subscribers: 224 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.6 days
Mean response time: 118.6 days
90th percentile: 341.7 days
Tracked items: 24

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: 791 days
Stale 30+ days: 28
Stale 90+ days: 27

Recent activity

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

Top labels

  • status: help wanted (6)
  • type: bug (3)
  • difficulty: unknown or n/a (2)
  • type: community enhancement (2)
  • difficulty: medium (1)
  • type: question (1)
  • type: support (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

sendgrid-nodejs is a Node.js API library that enables developers to integrate Twilio SendGrid's email and communication services into their applications.

The library solves the problem of sending transactional emails and accessing SendGrid's Web API v3 endpoints from Node.js applications. This modular approach allows developers to install only the packages they need rather than a monolithic dependency.

Developers should choose this library if they are building Node.js applications that require email delivery or need to interact with SendGrid's broader API surface. The mail package is the right choice for projects focused solely on sending email, while the client package suits applications that need to manage contacts, templates, suppression lists, or other SendGrid features. The library is officially maintained by Twilio SendGrid with community contributions encouraged, making it suitable for production use where vendor support matters.

The project maintains a structured contribution process with clear guidelines for feature requests, bug reports, and code improvements. A migration guide documents breaking changes between major versions, helping developers plan upgrades. The maintainers actively solicit community input through issues and pull requests to guide development priorities. Troubleshooting documentation is provided to help developers resolve common issues independently.