You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to request the CodeRabbit GitHub App for the Node.js org, under their free plan for open source. Like in #1105, I'd say we start small, with a few repos that opt in, and see how it goes before opening it up further.
Why
We don't have a good automated first-pass reviewer today:
The Copilot PR reviews are mostly noise, and I'd rather replace them than keep both.
The Anthropic oss-scanner is capped at 4 active PRs (anthropics/oss-scanner#1282), so it can't really onboard repos at our scale.
CodeRabbit reviews each PR (summary, line comments, suggested fixes), it's free for open source, and it's already used by projects like Bun, pnpm, Nuxt, Vue and Ghost. The review config lives in a .coderabbit.yaml per repo, so each team can tune it or turn it off.
Proposal
Install the App on the org, limited to the repos that ask for it. nodejs/doc-kit and nodejs/nodejs.org volunteer as first ones.
Keep it advisory: no required checks, and humans stay the reviewers.
Revisit after a month or so, and drop it if it's not helping.
Open questions
Is the TSC / Admin fine with the App's permissions? I'll add the exact list from CodeRabbit's docs here once I've double checked it against what the install screen asks for.
Should we turn off the Copilot auto-review at the same time on those repos?
Pullfrog (OSS, bring your own tokens) and Greptile were also mentioned as alternatives. Happy to compare if anyone feels strongly.
Should we wait for Cursor to get back to us in that Slack channel (if someone doesn't have access to the channel I'm referring to and need it, please DM me)?
I mean, we are using Cursor for the IDE right? I recall we also had BugBot but... But unsure how it stacks against CodeRabbit and the differences and what we should enable where 👀
4. @ovflowd I meant for BugBot, we don't need both, so we should wait to hear back from Cursor
Right, I mean I prefer having both and giving the choice to each individual team of what they want to use in their repository... I guess? But is BugBot still working?
Activity
avivkeller commentedon Nov 2, 2026
Should we wait for Cursor to get back to us in that Slack channel (if someone doesn't have access to the channel I'm referring to and need it, please DM me)?
ovflowd commentedon Nov 2, 2026
I mean, we are using Cursor for the IDE right? I recall we also had BugBot but... But unsure how it stacks against CodeRabbit and the differences and what we should enable where 👀
nschonni commentedon Nov 2, 2026
FYI, if you are using that IDE, you might want to see if you were impacted by https://www.bleepingcomputer.com/news/security/malicious-claude-code-extension-on-cursor-planted-ssh-backdoors/
avivkeller commentedon Nov 2, 2026
@ovflowd I meant for BugBot, we don't need both, so we should wait to hear back from Cursor
ovflowd commentedon Nov 2, 2026
Nah, wasn't. I don't use the Claude Extension there.
ovflowd commentedon Nov 2, 2026
Right, I mean I prefer having both and giving the choice to each individual team of what they want to use in their repository... I guess? But is BugBot still working?