adb6b3b · 30,637 commits · 13,286 files
Issued 2026-10-22
Reads strong: 4 of 6 rated dimensions are strong, 2 are adequate and none is significant.
104 checks ran across 6 assessable dimensions. Security & Reliability Posture and Product & Engineering Maturity are adequate. 1 finding is worth checking first. 14 findings, each with evidence. One dimension cannot be assessed without an acquirer.
This repository reads strong. Show it in your README: the badge links to a page where anyone can check the reading. If you embed it: link it to the report, remove it if the report is delisted, and do not present it as a certification or an endorsement.
[](https://borehole.dev/verify/2BKNRY4FSQ09?via=badge)- 04.62 Releases are cut from another branch than the one surveyed
- 05.61 Part of the code is under a separate licence: apps/meteor/ee/ apps/meteor/ee/LICENSE
Borehole's proprietary scoring is calibrated across hundreds of repositories. Each finding here reads significant, but its check has not yet held up often enough in that calibration to rate significant on its own. If one holds when someone checks it, it is significant.
- 04.3 264 direct dependencies in a single manifest
- 2 findings from checks Borehole's calibration found wrong more often than right are no longer published.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | strong | |
| 02 | Engineering Process & SDLC Maturity | strong | |
| 03 | Organization & Key-Person Risk | strong | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | strong | |
| 07 | Fit with the Acquirer | not assessable |
- 13% of non-merge commits carry any trailer at all
- low trailer coverage: the convention may not be in consistent use
- no widespread author/committer date divergence
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑packages/rest-typings/src/v1/omnichannel.ts is 4,877 lines, 128× this codebase's median file
adequateThe median source file here is 38 lines. 31 files exceed 1,000 lines, the largest being 4,877. 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.
A note that does not affect this rating: measured against its own codebase's median, it is below the 85th percentile of 382 surveyed projects' largest files, where this check begins to count.
| line-count | packages/rest-typings/src/v1/omnichannel.ts:1 — 4,877 lines (128× median) |
| line-count | packages/livechat/src/lib/emoji/emojis.ts:1 — 4,631 lines (121× median) |
| line-count | packages/models/src/models/Users.ts:1 — 3,423 lines (90× median) |
| line-count | packages/models/src/models/LivechatRooms.ts:1 — 2,782 lines (73× median) |
| line-count | apps/meteor/server/api/v1/users.ts:1 — 2,413 lines (63× median) |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Engineering Process & SDLC Maturity
02 · strong · ratings ↑Tests are retried until they pass
adequateThe suite is configured to retry failing tests (apps/meteor/tests/end-to-end/api-livechat/19-business-hours.ts). 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.
A note that does not affect this rating: notes like it are common in well-run projects.
| apps/meteor/tests/end-to-end/api-livechat/19-business-hours.ts | apps/meteor/tests/end-to-end/api-livechat/19-business-hours.ts:967 — test retry |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Organization & Key-Person Risk
03 · strong · ratings ↑No finding. 10 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · adequate · ratings ↑264 direct dependencies in a single manifest
adequate worth checking firstapps/meteor/package.json declares 264 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
The check that found this reads significant, but it has not yet held up often enough in Borehole's calibration to rate a finding significant on its own. Opening apps/meteor/package.json and the 3 other files it cites settles it. If it holds when someone checks it, this finding is significant.
| direct-dependencies | apps/meteor/package.json — 264 declared |
| direct-dependencies | ee/apps/omnichannel-transcript/package.json — 28 declared |
| direct-dependencies | apps/uikit-playground/package.json — 27 declared |
| direct-dependencies | ee/apps/ddp-streamer/package.json — 26 declared |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
2 jobs are each done by more than one library
adequateWithin a single package: dates: date-fns, moment; utility belts: lodash, underscore. Each duplicate is bundle size, two ways of doing the same thing in one codebase, and two upgrade paths to maintain. It is usually the residue of a migration that stopped halfway.
| apps/meteor/package.json | apps/meteor/package.json — several libraries per job |
| ee/apps/ddp-streamer/package.json | ee/apps/ddp-streamer/package.json — several libraries per job |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
31 files still carry code deprecated more than two years ago
adequate31 files were marked deprecated over two years ago and still are, the oldest since Apr 2022. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| packages/core-typings/src/IRoom.ts | packages/core-typings/src/IRoom.ts — deprecated since Apr 2022 |
| packages/core-typings/src/IMessage/IMessage.ts | packages/core-typings/src/IMessage/IMessage.ts — deprecated since Apr 2022 |
| packages/model-typings/src/models/IRolesModel.ts | packages/model-typings/src/models/IRolesModel.ts — deprecated since Jul 2022 |
| apps/meteor/definition/externals/global.d.ts | apps/meteor/definition/externals/global.d.ts — deprecated since Aug 2022 |
| packages/core-typings/src/ILivechatDepartmentRecord.ts | packages/core-typings/src/ILivechatDepartmentRecord.ts — deprecated since Feb 2023 |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Releases are cut from another branch than the one surveyed
adequateThe newest release, 8.9.0, is not on the branch this survey read; the newest release on it is 8.8.1. The shipped product may differ from what this report describes. Survey the release branch too.
A note that does not affect this rating: notes like it are common in well-run projects.
| 057a927d9 | tag 8.9.0 |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Security & Reliability Posture
05 · adequate · ratings ↑The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
| apps/meteor/vite/vite.config.mts | apps/meteor/vite/vite.config.mts:262 — source maps in a production build |
| packages/css-in-js/rollup.config.mjs | packages/css-in-js/rollup.config.mjs:41 — source maps in a production build |
| packages/emitter/rollup.config.mjs | packages/emitter/rollup.config.mjs:13 — source maps in a production build |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Part of the code is under a separate licence: apps/meteor/ee/
adequateA directory named for a paid edition carries its own licence. That code is usually not open source even where the rest is; what the buyer may do with each part differs.
| apps/meteor/ee/LICENSE | apps/meteor/ee/LICENSE — licence: unrecognised |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
The build runs third-party code it does not pin
adequate2 steps pipe a download straight into a shell. 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.
A note that does not affect this rating: notes like it are common in well-run projects.
| scripts/check-deps.sh | scripts/check-deps.sh:77 — download piped into a shell |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
2 shell commands built from strings
adequate2 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| apps/meteor/packages/rocketchat-livechat/plugin/build-livechat.js | apps/meteor/packages/rocketchat-livechat/plugin/build-livechat.js:20 — command run through a shell |
| apps/meteor/packages/rocketchat-livechat/plugin/build-livechat.js | apps/meteor/packages/rocketchat-livechat/plugin/build-livechat.js:22 — command run through a shell |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
29 locked dependencies have published vulnerabilities, 7 high or critical
adequate29 of 3,484 locked dependencies match 36 published advisories in OSV, 7 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| yarn.lock | yarn.lock — dompurify 3.4.16: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17 |
| yarn.lock | yarn.lock — storybook 9.1.20: GHSA-f2ph-cmg5-wxc8 (critical), fixed in 9.1.21 |
| yarn.lock | yarn.lock — braces 3.0.3: GHSA-vfj7-8cjw-p6xm (high) |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
17 places insert HTML from a variable without sanitising it
adequate17 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.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| apps/meteor/client/lib/createRichTextComposerAPI.ts | apps/meteor/client/lib/createRichTextComposerAPI.ts:57 — HTML from a variable |
| apps/meteor/client/lib/emoji/emojiParser.ts | apps/meteor/client/lib/emoji/emojiParser.ts:30 — HTML from a variable |
| apps/meteor/client/lib/emoji/emojiParser.ts | apps/meteor/client/lib/emoji/emojiParser.ts:53 — HTML from a variable |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
22 advisories against this project in the last 24 months, 12 high or critical
adequateThe newest was published on 2026-08-21. 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 20 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 8.8.1. Answer lives in: the release you run, set against each fixed version.
A note that does not affect this rating: it describes the project's advisory record, and no advisory in it is known to affect the surveyed commit.
| CVE-2026-65645 | 2026-08-21: CVE-2026-65645 (moderate): Rocket.Chat in versions before 8.8.0, 8.7.1, 8.6.2, 8.5.3, 8.4.6. 8.3.8, 8.2.8, 8.1.8, and 7.10.15, the Meteor DDP methods getThreadsList and getThreadMessages |
| GHSA-6x96-99rg-wg67 | 2026-08-20: GHSA-6x96-99rg-wg67 (moderate), fixed in 8.2.8: Blind Server-Side Request Forgery (SSRF) In The downloadPublicImportFile Endpoint |
| GHSA-r3v3-v742-55j5 | 2026-08-20: GHSA-r3v3-v742-55j5 (moderate), fixed in 7.10.15: Arbitrary notify-user event injection via stream-notify-room-users forward (incomplete fix of GHSA-27jx) |
| GHSA-7c6v-m68v-v73r | 2026-08-20: GHSA-7c6v-m68v-v73r (low), fixed in 7.10.15: sendForgotPasswordEmail Meteor Method Lacks DDP Rate Limit |
| GHSA-4mvx-9h2h-hmg3 | 2026-07-11: GHSA-4mvx-9h2h-hmg3 (moderate), fixed in 7.10.14: Broken Access Control in channels.convertToTeam Allows Unauthorized Conversion of Public Channels into Teams |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Observability & Operations
06 · strong · ratings ↑4 of 27 deployed images carry no version, or `latest`
adequate4 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| development/docker-compose-monitoring.yml | development/docker-compose-monitoring.yml:15 — image without a version |
| development/docker-compose-monitoring.yml | development/docker-compose-monitoring.yml:58 — image without a version |
| docker-compose-ci.yml | docker-compose-ci.yml:236 — image without a version |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Fit with the Acquirer
07 · not assessable · ratings ↑Not rated: structurally not assessable from a repository. What a person adds here.
Check it on the running system
4 checks against the running system follow from the findings above: what a buyer's engineer will try, how to run it first, and what to have ready. A paid survey of this repository includes them.
A paid survey of a public repository is also reviewed: a language model reads each finding against the code and withdraws only findings it judges the code contradicts, each listed with its reason. The review is a language model's reading of the findings against the code, and it can be wrong. It never adds a finding, never raises a band, and never removes a finding from a proven check or an advisory that affects the surveyed version.
What a person adds
The survey reads what the repository can show. The code cannot settle these questions, and on them this report states nothing. Each says where its answer lives: your own engineer, the company, or an assessor you choose can settle it. Questions marked measured open with something this repository shows.
Architecture & Codebase — including AI provenance
01 · full coverage- measured The tree carries design documentation (apps/meteor/tests/e2e/fixtures/files/diagram.drawio and 8 more). Does it match what the team believes today? Ask them to walk through it against the code.
- Is the architecture right for the next three years of the product?
- Were the home-grown components reasonable choices when they were made, and are they now?
Engineering Process & SDLC Maturity
02 · high coverage- Is review real or a rubber stamp? Comment depth and time to approve need the pull request history.
- Is delivery planned and measured, or heroic?
- How are incidents run, reviewed and learned from?
Organization & Key-Person Risk
03 · partial coverage- measured 1,020 people have committed here. Which of them are you acquiring, and which are you replacing?
- Who mentors whom, and would that survive a departure?
- Can the team grow, and who stands behind the top three contributors?
- Is the seniority mix sound, and will pay survive your salary bands?
- Is the pace sustainable? Commit times cannot say: git keeps no reliable local time.
- Does the team want to stay after close?
- How are decisions made and disagreements resolved?
Product & Engineering Maturity
04 · minimal coverage- Can this team deliver the stated roadmap on the stated timeline?
- Does leadership know about the debt, and is time budgeted to repay it?
- Is the engineering shape consistent with the commercial story?
Security & Reliability Posture
05 · partial coverage- measured 05.5 found credential-shaped strings in this repository. Was each one revoked at the provider? Deleting it from the code revokes nothing; only the provider's audit log shows that it was.
- measured No threat model is in the tree of what looks like a running service. Does one exist elsewhere, and who owns it?
- What has actually broken, how often, and how badly?
- What did external testing find, and was it fixed?
- What is the SOC 2, ISO 27001 or GDPR status, and where is the evidence?
Observability & Operations
06 · partial coverage- measured Nothing in the tree backs up or restores data. How is data backed up, and has a restore ever been rehearsed?
- measured No alert rule is defined in the repository. Where are alerts defined, who receives them, and when did one last fire?
- Are the dashboards opened, the alerts acknowledged and the pages answered?
- Are the service-level objectives actually met?
- Who carries the pager, and how often does it go off?
- What does it cost to run, and how much headroom is there?
Fit with the Acquirer
07 · none coverageNot rated: structurally not assessable from a repository.
- This is primarily a TypeScript codebase. Does your engineering organisation already run TypeScript in production, or would this be the first?
- The bulk of this system sits in packages/, apps/, ee/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (development/docker-compose-monitoring.yml and 18 more). Does that match your deployment and on-call model, or does it need rehosting first?
- What is your tolerance for the findings above remaining unaddressed for the first two quarters after close, given everything else that will compete for this team's time?
- Which of these systems duplicate yours, and which get retired?
- What will integration cost, and in what order?
- Where does the team land in your organisation, and who reports to whom?
- Are there earn-outs, retention packages or contractor IP to assign?
- Do customer contracts limit hosting, regions or vendors?
A human assessment is Borehole's own paid service, €12,000+ (total price is determined per engagement; travel billed at cost). It is not independent of this report: the same business produced both. It is a separate contract, with its own scope, terms and reliance.
Embed the badge
Tied to this commit and this date, and it fades after 90 days — an honest badge is one that expires. A repository with significant findings gets a neutral "read" badge rather than a red one: the library is where the range is visible, not someone else's README.
[](/r/rocketchat/rocket.chat/adb6b3b)If you embed it: link it to the report, remove it if the report is delisted, and do not present it as a certification or an endorsement.
Rejection log — 90 signals that ran and did not fire
Appendix: rejection log — 90 signals that ran and did not fire
Published on purpose. A signal that looked and decided not to fire has told you something, and this is the calibration data behind every threshold above.
Looked, and found nothing — 73
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 56,211 · top5 share 0.023 |
| 04.debt_markers | debt markers are sparsemarkers 744 · per kloc 0.59 · lines read 1,255,818 |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.485 · early test per code 0.097 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.682 · early delete per insert 0.582 |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 04.fixes_with_tests | fixes usually come with a testfixes 1,364 · share 0.514 · with tests 701 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.compat_layers | little code is kept for the old wayshare 0.001 · code files 8,380 · compat files 9 |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 87 |
| 06.structured_logging | a structured logging library is referencedmatches 14 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.telemetry_depth | the service is visible in more than one way |
| 06.correlation_ids | a request can be followed through the logstracing True · request id sites 10 |
| 06.error_reporting | an error reporter is initialisedinitialised 2 · config files 0 |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 0 |
| 06.environment_branching | environment differences live in configurationsites 2 |
| 06.release_markers | releases are markedtags last year 154 · release commits 81 · changelog commits 120 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 11.4 · window last 24 months · authors 1,020 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 1,020 · active 12mo 95 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 1,020 · directories 4 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 1,020 · one off share 0.517 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 1,020 · top share less than a quarter · top contributor last committed within the last three months |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 121 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.bus_factor_trend | the team has not narrowed to one person |
| 03.joiners_and_leavers | the team is not shrinkingleft 6 · joined 17 · regular last year 43 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 114 · window last 24 months · with tracked 0 |
| 02.ci_presence | CI configuration is present in the working treecount 17 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 2,407 · source 10,785 · test ratio 0.223 |
| 02.release_cadence | tags are presenttags 1,307 |
| 02.conventional_commits | commit subjects generally carry contentsampled 24,851 · low content share 0.027 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 17 · with tests 3 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 130 · test files 3,006 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 17 |
| 02.revert_share | change is rarely undoneshare 0.003 · reverts 12 · recent commits 3,880 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 2 · commits since 1 · days since lockfile changed 0 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 99 · ci configs 17 · product files 8,380 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.032 · commits 3,257 · over 2000 lines 103 |
| 01.burst_import | the largest burst was data and assets (86% of it), which explains the rate: translations arrive from a vendor in bulk, dependencies and generated code are committed whole, a merged pull request is dated when it merged, not when it was written, a branch merged by a merge commit was reviewed as one piece, and an export or mirror tool dates history when it replays itlargest commits 0285f08..cafe0b6 · bursts explained 3 · largest net added 3,894 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 26 · share of insertions 0.0 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 24.17 · repeat share 0.062 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 8,822 · write once share 0.4 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0087 · product files 8,373 · distinct blocks 355,850 |
| 01.swallowed_errors | errors are rarely thrown awayloc 1,267,556 · files 1 · per kloc 0.0 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 3 |
| 01.unfinished_migration | no language migration is stalled halfway |
| 01.weights_in_git | no model weights are committedfiles 0 |
| 05.committed_secrets | no credential-shaped strings outside test and fixture pathsnote the working tree only; the history is 05.5 · patterns 8 · files read 11,879 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.dependency_pinning | a lockfile is committed, so builds are reproduciblelockfile True |
| 05.license_present | a licence file is presentfound True |
| 05.container_runs_as_root | every shipped Dockerfile drops to a non-root user or builds on a non-root base imagedockerfiles 1 |
| 05.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.migration_reversibility | migrations can be rolled backshare 0.0 · migrations 61 · irreversible 0 |
| 05.sql_from_strings | no SQL is assembled from strings in product codefiles 0 · sites 0 · value interpolated 0 |
| 05.unsafe_deserialization | no code-executing deserialiser in product codesites 0 |
| 05.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 · behind a setting or built here 0 |
| 05.credentials_in_deploy_config | deployment configuration references secrets, never holds themfiles 0 · sites 0 |
| 05.public_env_secret | only publishable values carry a public prefixnames 0 · sites 0 · not secrets 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.license_manifest_conflict | manifest and licence file agree on MITlicense MIT |
| 05.license_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.license_grant_unclear | the licence is recognisable as MITclass permissive · license MIT |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 273 · added in two years 122 · removed within 60 days 2 |
| 04.ci_platforms_dropped | no platform was dropped from CI in the last two years |
| 04.repository_status | the README's first screen states no end, move or freezestatements 0 |
| 02.development_elsewhere | nothing says development happens elsewhereno pr statements 0 · mirror statements 0 · replayed commit share 0.0 |
| 05.licence_changes | the root licence has not changed in the history readlicence versions 1 · unreleased changes 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 1.5 · days since last tag 6 · commits last 90 days 669 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 17
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.schema_churn | no schema migrations to read |
| 06.print_logging | a frontend: console output is the browser's, not the server's |
| 06.alert_rules | no alert rules in the repository; they may live in a console |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.outbound_timeouts | not assessed for TypeScript or TSX, the languages the product is written in: this check's patterns read other languages only |
| 05.resource_limits | no Kubernetes workload manifests |
| 05.cleartext_traffic | not a mobile app |
| 05.dataset_provenance | not a data or machine-learning repository |
| 05.license_copyleft_inherited | no third-party code is committed to this repository, so the licences it depends on are resolved at build time and are not readable here |
| 04.flags_accumulating | few or no feature flags in the history |
| 04.api_versions_coexisting | one API version is served, or none |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; OSV npm @rocket.chat/apps-engine (an empty record for a package published here), OSV npm @rocket.chat/core-typings (an empty record for a package published here), OSV npm @rocket.chat/css-in-js (an empty record for a package published here), OSV npm @rocket.chat/css-supports (an empty record for a package published here), OSV npm @rocket.chat/ddp-client (an empty record for a package published here), OSV npm @rocket.chat/desktop-api (an empty record for a package published here), OSV npm @rocket.chat/eslint-config (an empty record for a package published here), OSV npm @rocket.chat/media-signaling (an empty record for a package published here), OSV npm @rocket.chat/rest-typings (an empty record for a package published here) did not |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited list |
Anyone can check this report against the authoritative record — click the stamp, or enter 2BKN-RY4F-SQ09 at borehole.dev/verify.
The code commits to the 106 checks this run performed, the bands they produced, and the commit they were read at. It does not cover checks written since.
Put the mark in your README
The image is wrapped in a link to the verification page, so a reader can check it rather than take it on trust. If you embed it: link it to the report, remove it if the report is delisted, and do not present it as a certification or an endorsement.
[](https://borehole.dev/verify/2BKNRY4FSQ09?via=badge)
Where this scan ran
This scan ran on ordinary cloud infrastructure (cloud-run), not in a hardware-isolated confidential VM. Nothing about it is attested by Google.
What an attested survey proves, and what it does not.
What this scan did with the repository — 7 steps
Written by the steps themselves as they ran, not described afterwards. A hand-written account of a data flow drifts the first time somebody changes the flow and not the account.
| At | Step | Detail |
|---|---|---|
| 0.0s | read repository metadata from the GitHub API | size mb: 2131.1authenticated: False |
| 146.6s | cloned the repository to a temporary directory | depth: full |
| 216.2s | read the git history | commits: 30637tracked files: 13286 |
| 582.1s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 582.1s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 798.8s | kept the facts, never the source, for re-reading under new checks | |
| 798.8s | deleting the working copy |
Total 798.8s ·source content sent off this machine: none · calls to a language model: 0 · the clone was deleted when the survey ended
An automated reading of a repository's code and its history up to one commit, with public advisory records. It may be wrong, it is not legal, financial, investment or security advice, and it does not replace diligence by a qualified person. It is provided for information: nobody may rely on it (Borehole's terms, section 3).