Analysis updated 2026-07-09 · repo last pushed 2020-02-13
Automatically warn when a pull request modifies source files without updating the changelog.
Block pull requests that are missing required test files for changed code.
Verify that open-source contributors have signed a CLA before their PR can merge.
Share a common set of code review rules across multiple repositories using the plugin system.
| juanpe/swift | 0xhassaan/nn-from-scratch | 0xzgbot/hermes-comfyui-skills | |
|---|---|---|---|
| Stars | — | 0 | 0 |
| Language | — | Python | — |
| Last pushed | 2020-02-13 | — | — |
| Maintenance | Dormant | — | — |
| Setup difficulty | moderate | moderate | easy |
| Complexity | 3/5 | 4/5 | 1/5 |
| Audience | developer | developer | designer |
Figures from each repo's GitHub metadata at analysis time.
Requires a Swift environment and integration with a CI pipeline like GitHub Actions.
Danger Swift is a tool that automates the repetitive parts of code review. If you've ever found yourself leaving the same comment over and over on pull requests, "you forgot to update the changelog," "this file needs tests," "fix your formatting", this tool handles those automatically. It runs as part of your continuous integration pipeline and posts comments directly on pull requests, so reviewers can focus on the actual logic rather than policing house rules. You write a "Dangerfile" in Swift that inspects metadata about each pull request: which files changed, what lines were added or removed, who opened it, and so on. Based on that information, your Dangerfile can post messages, warnings, or even block the PR from merging if something critical is missing. For example, the README shows a rule that checks whether someone modified source files without updating the CHANGELOG, if so, it leaves a warning comment automatically. Teams using Swift who want to enforce project conventions without nagging people would get the most out of this. A startup with a small engineering team might use it to make sure every PR includes a test file, or that nobody accidentally commits debug code. Open-source maintainers could use it to verify that contributors have signed a CLA or followed branding guidelines. The plugin system lets you share rules across multiple repositories, so an organization can codify its standards once and reuse them everywhere. The project is specifically the Swift flavor of a broader tool called Danger (the original is written in JavaScript). It's worth noting that you can run it on macOS or Linux, and it integrates with GitHub Actions. The README points to the main Danger website for full documentation rather than covering everything itself.
Danger Swift automates repetitive code review tasks by running a Swift file in your CI pipeline that checks pull requests and posts comments, warnings, or blocks merges based on your custom rules.
Dormant — no commits in 2+ years (last push 2020-02-13).
No license information was provided in the explanation.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.