A record of public website updates and published engine releases. Cloud plans are kept separate from released software.
Engine · v3.0.5
Tests in TypeScript and JavaScript count as callers
Each Jest, Vitest and Mocha test now owns the calls in its callback, as a function named after its title, such as it: accepts two. arbor callers lists those tests, and arbor diff and check count them among the tests that exercise a change. MCP tool results give file paths relative to the project root instead of absolute paths from your machine.
GitHub, npm and crates.io all publish v3.0.5. Saved graphs rebuild once on first use.
Turn on checks for a repository, and each new commit on a pull request gets one “Arbor impact” check: the entry points the change reaches, the called functions with no test found, where to start reading with CODEOWNERS owners, and advisories for package versions the pull request added or updated in Cargo.lock, package-lock.json or npm-shrinkwrap.json. Each pull request uses one analysis, and new commits on it are free in the same billing period, or during the trial.
On Team, rules in .arbor/checks.yml can fail the check. A member with write access can override it for a commit, and Arbor records who and when.
Cloud
Arbor Cloud opens
Sign in with GitHub, connect a repository through the Arbor GitHub App and analyze a pull request you choose. Each run saves a private report of what the change reaches.
Each GitHub account starts with 3 free analyses. Developer ($19) and Team ($79) are monthly plans per workspace, with Razorpay taking the payment.
arbor diff no longer marks a class or module as modified because one of its methods changed, and an edit that only adds comments or blank lines no longer marks anything modified. Impact comes from callers alone, and the report names each modified symbol with its file, line and caller count. Rust method calls resolve through the receiver’s type where the code states it. .arbor/ now keeps itself out of git, and arbor hook claude no longer replaces a file it can’t read.
GitHub, npm, and crates.io all publish v3.0.4. Its Linux binaries need glibc 2.28 instead of 2.39, each release now includes SHA256SUMS and a signed provenance attestation, and arbor doctor flags an older arbor that runs ahead of a newer install on PATH.
The privacy notice and terms now cover Cloud accounts before they open: GitHub sign-in, repository access, what a report keeps and for how long, and deleting your account. Those parts apply only once accounts open, and we haven’t announced a date. The privacy notice also says what the open-source engine keeps on your machine.
The security page now explains how Cloud stays closed and which local ports the engine opens, and a new guide covers receipts for Claude Code turns.
Calls through Rust paths, associated functions, and macro arguments now resolve. arbor diff gives each modified symbol its own blast radius and lists new code separately. A graph built on another branch or by an older version is refreshed instead of answering. Classes gain inheritance edges, and call cycles no longer dominate the ranking.
GitHub, npm, and crates.io all publish v3.0.3. Its Linux binaries need glibc 2.39; the installation guide covers older systems.
The published engine release improves how calls are matched by considering imports before nearby declarations. The release notes describe the changes and remaining limitations.
GitHub release binaries were v3.0.0. The npm and crates.io channels remained at v2.6.0 until v3.0.3.