usebruno/bruno: technical due diligence, read from its repository

The median source file here is 89 lines. 30 files exceed 1,000 lines, the largest being 4,532. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.

The suite is configured to retry failing tests (packages/bruno-cli/tests/integration/run-typed-persistence.spec.js). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.

The newest release, v4.3.0, is not on the branch this survey read; the newest release on it is v3.0.1. The shipped product may differ from what this report describes. Survey the release branch too.

packages/bruno-app/.env.production is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.

4 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.

16 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.

The root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.

The newest was published on 2026-09-04. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 5 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 3.0.1. Answer lives in: the release you run, set against each fixed version. GHSA-658g-p7jg-wx5g (critical) is fixed in the surveyed commit; which release carries it cannot be told from this history, which does not place the release users run. Answer lives in: the version you run. The record is incomplete: NVD: 2 records name bruno with nothing tying them to this repository (CVE-2017-5589, CVE-2025-23988).

Nothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.