Repository navigation
v0.1.4
Install: npx @error-path/opendrs score, or keep uses: error-path/opendrs@v0 in your workflow (v0 now points at this release).
- Published to npm as
@error-path/opendrs.
npm refuses the unscoped nameopendrsas too close to an existing package. Run the CLI with
npx @error-path/opendrs scoreand the MCP server withnpx -y @error-path/opendrs mcp; the
command it installs is stillopendrs.npx github:error-path/opendrskeeps working. - Fixed:
blast.public_surfaceevidence reported line numbers one too low after a blank context
line that git printed without its leading space (diff.suppressBlankEmpty). The diff walkers in
the blast, content-block and SZZ code now share one helper that counts hunk lines the way the
diff parser does.
Ideas from Meta's DRS paper (arXiv 2410.06351) and its RADAR auto-review funnel (arXiv 2605.30208).
- New signal
size.comment_only(prior weight -2.0). It is 1 when every added or deleted line is
blank or a plain comment in the file's own syntax, and no file is renamed or binary. A lone/*
or*/(which can switch code on or off), a directive comment (//go:embed,// @ts-nocheck,
# type: ignore, a shebang) and any line in a language without a known comment syntax count as
code. Meta notes that a comment-only change "has
no risk" even on a risky path. A calibrated model gives the signal no weight until you run
opendrs calibrateagain. freezes: windows of weekdays and/or dates in a timezone. While one is active, auto-approval is
suspended, or held to a strictergreen(Meta's weekend gate and "code chill"). Tiers and labels
do not change.content.block: regexes checked against every added line. A match sends the PR to a human, and
the reason namesfile:line(RADAR's blocklisted code phrases).- The Action never auto-approves a draft PR, or a PR where a reviewer's latest review requests
changes. - When a green PR's earlier approval is withdrawn, for example by a freeze or a sample, the
dismissal message names the rule instead of "Risk increased".
Full Changelog: v0.1.3...v0.1.4