About Danger
Danger runs as part of your continuous integration process and gives teams a way to automate the repetitive parts of code review. Instead of reviewers repeatedly pointing out the same omissions, a Danger rule file codifies the team's norms and comments on the pull request or merge request automatically. It is written in Ruby and released under the MIT license.
Typical rules include requiring a changelog entry, requiring links to Trello or JIRA in the pull request body, enforcing descriptive labels, watching for common anti-patterns, highlighting interesting build artifacts, and giving specific files extra attention. It works with GitHub, GitLab, and Bitbucket and runs on common CI services, and a plugin system lets the community share reusable checks.
The idea is to leave humans free to think about harder problems such as design and correctness. Danger suits engineering teams of any size that want consistent pull request etiquette without relying on reviewers to remember every convention.
Key features
- Automated pull request checks in CI
- Enforce changelog entries and PR descriptions
- Require labels and tracker links
- Works with GitHub, GitLab, and Bitbucket
- Plugin system for shared rules
- Rules written as Ruby code
Good fit for
- →Enforcing team conventions on every pull request
- →Reducing repetitive review comments
- Built with
- Ruby
- Tags
- code-review
- ci
- automation
- ruby
- pull-requests
- github
- gitlab
- developer-tools
Danger: questions and answers
- What is Danger used for?
- Danger is a Ruby tool that runs in CI to automate routine code review chores, such as enforcing changelogs, labels, and links in pull request descriptions. It is a good fit for enforcing team conventions on every pull request and reducing repetitive review comments.
- Is Danger open source?
- Yes. Danger is open source under the MIT licence. Its source code is on GitHub at danger/danger and is written mainly in Ruby.
- Is Danger free?
- Yes. Danger is open source, so the software itself is free to use.
- What are some alternatives to Danger?
- Similar open-source tools in the CI/CD & DevOps category include Danger JS, reviewdog and GitLab. SaaS products in the same category include Mergify, GitHub Actions and AWS CodeDeploy.
- Is Danger actively maintained?
- Yes. The most recent commit to Danger was on 29 July 2026, and the latest release is v9.6.1, published on 29 July 2026. The project has 5.7k stars on GitHub.
Open-source alternatives to Danger
See all
Danger JS
CI/CD & DevOps
⚠️ Stop saying "you forgot to …" in code review
MIT★ 5.5k
reviewdog
CI/CD & DevOps
🐶 Automated code review tool integrated with any code analysis tools regardless of progra
MITvs Codacy★ 9.6k
GitLab
CI/CD & DevOps
GitLab CE Mirror | Please open new issues in our issue tracker on GitLab.com
OSSvs GitHub★ 25k
GitHub Agentic Workflows
CI/CD & DevOps
GitHub Agentic Workflows
MIT★ 5.3k
Kache
CI/CD & DevOps
Zero-copy, content-addressed Rust build cache for Rust, C/C++ and more. No copies, no wast
Apache-2.0★ 1k
Ship.js
CI/CD & DevOps
Take control of what is going to be your next release.
MIT★ 776
SaaS alternatives to Danger
See all
Mergify
CI/CD & DevOps
Merge queue and pull request automation for GitHub repositories
SaaS
GitHub Actions
CI/CD & DevOps
GitHub Actions is GitHub's built-in automation and CI/CD service for building, testing and deploying code through workflows triggered by repository events.
SaaS
AWS CodeDeploy
CI/CD & DevOps
AWS service that automates application deployments to EC2, Lambda and on-premises servers
SaaS
Bitbucket
CI/CD & DevOps
Git repository hosting with pull requests and built-in Pipelines CI/CD
SaaS
Buddy
CI/CD & DevOps
Visual CI/CD tool for building, testing and deploying web projects
SaaS
CAST AI
CI/CD & DevOps
Kubernetes automation platform for cost optimization and autoscaling
SaaS

