danger/danger-js

⚠️ Stop saying "you forgot to …" in code review

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 10 minutes ago
Added to GitGenius on September 12th, 2026
Created on August 20th, 2016
Open Issues & Pull Requests: 162 (+0)
GitHub issues: Enabled
Number of forks: 381
Total Stargazers: 5,510 (+0)
Total Subscribers: 24 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Danger JS is a code review automation tool that runs after CI to enforce team conventions and codify pull request etiquette.

The tool solves the problem of repetitive code review comments by automating checks for common patterns and team norms. It runs as a step in your CI pipeline and can inspect pull request metadata, changed files, and build artifacts to apply rules specific to your team's culture. Rather than requiring reviewers to repeatedly mention the same issues, Danger codifies these checks as executable rules that run automatically on every pull request.

Danger JS works with major code hosting platforms including GitHub, BitBucket Server, and BitBucket Cloud, and integrates with numerous CI systems such as Travis CI, Circle CI, GitHub Actions, Jenkins, GitLab CI, and many others. You can use it to enforce changelog updates, require links to issue trackers in PR descriptions, validate labeling practices, detect anti-patterns, highlight build artifacts, or warn when critical files change. The tool is designed for teams that want to move routine validation out of human review and into automated checks, freeing reviewers to focus on substantive code quality issues. The project provides a plugin system to share common rule implementations across teams.

The project maintains active development with regular commits and ongoing issue tracking. The codebase is written in TypeScript and includes automated testing and linting that run on push. Release management is controlled through a restricted tag-based process. The maintainers keep short-term priorities visible in the issue tracker and maintain a separate vision document for longer-term direction.