206c725 · 50,000 commits · 19,368 files
Issued 2026-10-22
Elastic-2.0 since 2021-09-27: source available, not open source; offering it as a managed service is not allowed.
1 of 6 assessable dimensions carries significant findings, 3 are adequate and 2 are strong. 1 finding is worth checking first. 21 findings, each with its evidence: the commit, path and lines it rests on, or, when something is missing, what was looked for. One dimension cannot be assessed without an acquirer.
- 04.61 No release for 12 months while development continues
- 05.66 The licence is Elastic-2.0: source available, not open source LICENSE:1
- 05.60 Relicensed: MIT → Elastic-2.0 (2021-09-27) LICENSE.md
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.
- 05.26 117 locked dependencies have published vulnerabilities, 86 high or critical in what ships
- 4 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 | significant findings | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 42% 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
- the declared share is neither decisive nor negligible, so the true figure is more sensitive to undeclared work
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑airbyte-integrations/connectors/source-shopify/source_shopify/shopify_graphql/bulk/query.py is 3,763 lines, 63× this codebase's median file
adequateThe median source file here is 59 lines. 10 files exceed 1,000 lines, the largest being 3,763. 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 | airbyte-integrations/connectors/source-shopify/source_shopify/shopify_graphql/bulk/query.py:1 — 3,763 lines (63× median) |
| line-count | airbyte-integrations/bases/base-normalization/normalization/transform_catalog/reserved_keywords.py:1 — 3,277 lines (55× median) |
| line-count | airbyte-integrations/bases/base-normalization/normalization/transform_catalog/stream_processor.py:1 — 1,531 lines (25× median) |
| line-count | airbyte-integrations/connectors/source-google-ads/source_google_ads/components.py:1 — 1,301 lines (22× median) |
| line-count | airbyte-integrations/connectors/source-amazon-seller-partner/components.py:1 — 1,298 lines (22× 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 ↑No finding. 16 checks ran and none fired; the rejection log below says why each did not.
Organization & Key-Person Risk
03 · significant findings · ratings ↑Bus factor 1: recent work is concentrated in one contributor
significant findingsIn the last 24 months, one contributor authored three-quarters or more of 17,989 non-merge commits among 322 authors; across all 34,865 commits read, a quarter or more of 34,865. This is the single most expensive thing to discover after closing, and the repository cannot tell you whether that person is part of the transaction.
| git shortlog -sn | last 24 months: top author three-quarters or more of 17,989 commits; bus factor 1; 322 authors |
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 next contributor after the top one has not committed here for more than a year
adequateThe #2 contributor of the last three years (less than a quarter of the commits) has not committed here for more than a year, while the repository is still active. These are the people a buyer assumes would step up if the top contributor stopped. The history shows only that no commits of theirs landed here, not why.
| git shortlog -sn | the #2 contributor of the last three years (less than a quarter of the commits) has not committed here for more than a year |
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.
Regular contributors fell from 91 to 49 in a year
adequate53 people who committed regularly the year before made no commits in the last year, and 16 new regular contributors arrived. Ask whether the work they did is still covered.
| regular contributors by year | 91 then 49; 53 stopped committing, 16 began |
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.
Product & Engineering Maturity
04 · adequate · ratings ↑132 direct dependencies in a single manifest
adequatedocusaurus/package.json declares 132 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.
| direct-dependencies | docusaurus/package.json — 132 declared |
| direct-dependencies | airbyte-integrations/connectors/source-file/pyproject.toml — 18 declared |
| direct-dependencies | airbyte-integrations/connectors/source-s3/pyproject.toml — 10 declared |
| direct-dependencies | airbyte-integrations/connectors/destination-motherduck/pyproject.toml — 8 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.
11% of the code is legacy or compatibility code, the oldest 38 months old
adequate288 of 2506 source files sit in paths named legacy, compat, shim, polyfill or deprecated, and some have been there 38 months. That is usually a migration that never finished. Ask whether finishing it is planned, and what keeping both costs.
| airbyte-cdk/bulk/toolkits/legacy-source-integration-tests/src/testFixtures/resources/image_exists.sh | airbyte-cdk/bulk/toolkits/legacy-source-integration-tests/src/testFixtures/resources/image_exists.sh — legacy or compatibility code |
| airbyte-cdk/bulk/toolkits/legacy-task-load-avro/src/main/kotlin/io/airbyte/cdk/load/command/avro/AvroFormatCompressionCodecSpecification.kt | airbyte-cdk/bulk/toolkits/legacy-task-load-avro/src/main/kotlin/io/airbyte/cdk/load/command/avro/AvroFormatCompressionCodecSpecification.kt — legacy or compatibility code |
| airbyte-cdk/bulk/toolkits/legacy-task-load-avro/src/main/kotlin/io/airbyte/cdk/load/data/avro/AirbyteTypeToAvroSchema.kt | airbyte-cdk/bulk/toolkits/legacy-task-load-avro/src/main/kotlin/io/airbyte/cdk/load/data/avro/AirbyteTypeToAvroSchema.kt — legacy or compatibility code |
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.
No release for 12 months while development continues
adequateThe last tag, v2.0.0, was cut 371 days before the survey; the typical gap between releases was 34 days, and 5365 commits landed in the last 90 days. Users run the last release, not this code.
| 8b40981ae | last tag v2.0.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.
Effort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.80 to 1.19 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team. This was read from the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026) only; older history was not read.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| deletions-per-insertion | first half 0.80, second half 1.19 (split 2024-07-01) |
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.
Python 3.9 is past end of life
adequateThe code is pinned to Python 3.9 (end of life 2025-10-31). None of these receives security fixes any more; the first stopped on 2025-10-31. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| airbyte-integrations/connectors/source-python-http-tutorial/Dockerfile | airbyte-integrations/connectors/source-python-http-tutorial/Dockerfile — Python 3.9, end of life 2025-10-31 |
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.
6 files still carry code deprecated more than two years ago
adequate6 files were marked deprecated over two years ago and still are, the oldest since Mar 2024. 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.
| airbyte-cdk/java/airbyte-cdk/s3-destinations/src/main/kotlin/io/airbyte/cdk/integrations/destination/s3/parquet/ParquetSerializedBuffer.kt | airbyte-cdk/java/airbyte-cdk/s3-destinations/src/main/kotlin/io/airbyte/cdk/integrations/destination/s3/parquet/ParquetSerializedBuffer.kt — deprecated since Mar 2024 |
| airbyte-cdk/java/airbyte-cdk/core/src/main/kotlin/io/airbyte/cdk/integrations/destination/record_buffer/SerializableBuffer.kt | airbyte-cdk/java/airbyte-cdk/core/src/main/kotlin/io/airbyte/cdk/integrations/destination/record_buffer/SerializableBuffer.kt — deprecated since Mar 2024 |
| airbyte-cdk/java/airbyte-cdk/db-sources/src/main/kotlin/io/airbyte/cdk/integrations/source/relationaldb/state/LegacyStateManager.kt | airbyte-cdk/java/airbyte-cdk/db-sources/src/main/kotlin/io/airbyte/cdk/integrations/source/relationaldb/state/LegacyStateManager.kt — deprecated since Mar 2024 |
| airbyte-cdk/java/airbyte-cdk/db-destinations/src/main/kotlin/io/airbyte/cdk/integrations/destination/jdbc/AbstractJdbcDestination.kt | airbyte-cdk/java/airbyte-cdk/db-destinations/src/main/kotlin/io/airbyte/cdk/integrations/destination/jdbc/AbstractJdbcDestination.kt — deprecated since Mar 2024 |
| airbyte-integrations/connectors/destination-oracle/src/main/java/io/airbyte/integrations/destination/oracle/OracleNameTransformer.java | airbyte-integrations/connectors/destination-oracle/src/main/java/io/airbyte/integrations/destination/oracle/OracleNameTransformer.java — deprecated since Apr 2024 |
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 ↑7 Dockerfiles run the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
| no-USER-instruction | airbyte-cdk/bulk/core/base/src/testFixtures/resources/bastion/Dockerfile — runs as root |
| no-USER-instruction | airbyte-cdk/java/airbyte-cdk/core/src/main/resources/bastion/Dockerfile — runs as root |
| no-USER-instruction | airbyte-integrations/bases/base-java/Dockerfile — runs as root |
| no-USER-instruction | airbyte-integrations/bases/base-normalization/Dockerfile — runs as root |
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.
117 locked dependencies have published vulnerabilities, 86 high or critical in what ships
adequate worth checking first117 of 2,984 locked dependencies match 249 published advisories in OSV, 122 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.
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 airbyte-integrations/connectors/source-sftp-bulk/poetry.lock and the 2 other files it cites settles it. If it holds when someone checks it, this finding is significant.
| airbyte-integrations/connectors/source-sftp-bulk/poetry.lock | airbyte-integrations/connectors/source-sftp-bulk/poetry.lock — pillow 12.0.0: GHSA-332p-7hrc-92wf (critical), fixed in 13.0.0 |
| airbyte-integrations/connectors/source-gcs/poetry.lock | airbyte-integrations/connectors/source-gcs/poetry.lock — pillow 12.3.0: GHSA-332p-7hrc-92wf (critical), fixed in 13.0.0 |
| airbyte-integrations/connectors/source-azure-blob-storage/poetry.lock | airbyte-integrations/connectors/source-azure-blob-storage/poetry.lock — unstructured 0.10.27: GHSA-4mvj-m6j5-pmf7 (critical), fixed in 0.24.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.
The build runs third-party code it does not pin
adequate5 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.
A note that does not affect this rating: notes like it are common in well-run projects.
| .github/workflows/ai-breaking-change-review-command.yml | .github/workflows/ai-breaking-change-review-command.yml:90 — action pinned by tag |
| .github/workflows/ai-canary-prerelease-command.yml | .github/workflows/ai-canary-prerelease-command.yml:51 — action pinned by tag |
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.
48 outbound calls can wait forever
adequate48 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| airbyte-ci/connectors/ci_credentials/ci_credentials/google_api.py | airbyte-ci/connectors/ci_credentials/ci_credentials/google_api.py:35 — outbound call without a timeout |
| airbyte-ci/connectors/ci_credentials/ci_credentials/google_api.py | airbyte-ci/connectors/ci_credentials/ci_credentials/google_api.py:45 — outbound call without a timeout |
| airbyte-ci/connectors/ci_credentials/ci_credentials/google_api.py | airbyte-ci/connectors/ci_credentials/ci_credentials/google_api.py:83 — outbound call without a timeout |
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 SQL statements built from strings
adequate2 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| airbyte-integrations/connectors/destination-databend/destination_databend/writer.py | airbyte-integrations/connectors/destination-databend/destination_databend/writer.py:117 — SQL built from a string |
| airbyte-integrations/connectors/destination-firebolt/destination_firebolt/writer.py | airbyte-integrations/connectors/destination-firebolt/destination_firebolt/writer.py:211 — SQL built from a string |
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.
3 deserialisers that can run code
adequate3 places read data with a deserialiser that executes what it reads (`yaml.load` without a safe loader, pickle). That is safe on data the system wrote itself and remote code execution on anything else. 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.
| airbyte-integrations/bases/base-normalization/normalization/transform_catalog/transform.py | airbyte-integrations/bases/base-normalization/normalization/transform_catalog/transform.py:76 — code-executing deserialiser |
| airbyte-integrations/bases/base-normalization/normalization/transform_config/transform.py | airbyte-integrations/bases/base-normalization/normalization/transform_config/transform.py:50 — code-executing deserialiser |
| airbyte-integrations/connectors/source-s3/source_s3/utils.py | airbyte-integrations/connectors/source-s3/source_s3/utils.py:54 — code-executing deserialiser |
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 licence is Elastic-2.0: source available, not open source
adequateLICENSE grants Elastic-2.0: source available, not open source; offering it as a managed service is not allowed. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.
A note that does not affect this rating: it names the project's licence, a fact for the first screen rather than a weakness.
| LICENSE | LICENSE:1 — 44 lines, Elastic-2.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.
Relicensed: MIT → Elastic-2.0 (2021-09-27)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
A note that does not affect this rating: a licence change is a fact for the first screen, and only a narrowing of rights within two years of the surveyed commit costs "strong".
| 87e9c99ae | LICENSE.md — MIT from 2020-08-17 |
| f25542a14 | LICENSE — Elastic-2.0 from 2021-09-27 |
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 advisories against this project in the last 24 months, 2 high or critical
adequateThe newest was published on 2026-10-17. 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 2 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 2.0.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 2 records name airbyte with nothing tying them to this repository (CVE-2026-92203, CVE-2026-92204).
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.
| GHSA-g35w-6r6v-h4r7 | 2026-10-17: GHSA-g35w-6r6v-h4r7 (critical), fixed in 2.2.0: Remote code execution via Connector Builder custom components when unsafe code is disabled |
| CVE-2026-80049 | 2026-08-25: CVE-2026-80049 (high): Airbyte Platform resolves the workspace used for its authorization decision from a field the caller supplies. AuthorizationServerHandler copies recognised ident |
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 · adequate · ratings ↑No structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| logging-scan | searched 4,855 files for 10 structured logging libraries; 0 matched |
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.
No error reporter is wired in
adequateNothing 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.
A note that does not affect this rating: notes like it are common in well-run projects.
| error reporting | no error reporter initialised |
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
8 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 No architecture or design document is in the tree, across 9,872 product files. Where does the design live, and who holds it?
- 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 One contributor authored a quarter or more of the commits in this history. Is that person part of the transaction, and for how long after it?
- 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- measured 1,705 commits landed in the last year, against 16,249 the year before (-90%). Is that maintenance mode, a pivot, or fewer people working on it? The count looks the same for all three.
- measured No experiment tracking is configured in the repository. How was the shipped model trained and evaluated, and could it be reproduced?
- measured No model card is in the tree. What is the model's intended use, what was it trained on, and where does it fail?
- 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 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 Alert rules are defined in the repository. 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 Kotlin codebase, with Python alongside (30% of source files). Does your engineering organisation already run Kotlin in production, or would this be the first?
- The bulk of this system sits in airbyte-integrations/, airbyte-cdk/, docusaurus/. Which of your existing systems would each of those have to absorb or replace?
- 57% of lines added in the last 12 months (17% of lines added in the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026)) came through AI-declared commits. Does your organisation have a policy on inheriting and maintaining that code, and does your engineering team's tooling match how it was produced?
- The repository carries deployment configuration (airbyte-cdk/bulk/core/base/src/testFixtures/resources/bastion/Dockerfile and 34 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/airbytehq/airbyte/206c725)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 — 81 signals that ran and did not fire
Appendix: rejection log — 81 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 — 56
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few files, in the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026)files 45,624 · top5 share 0.016 · history read the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026) |
| 04.debt_markers | debt markers are sparsemarkers 341 · per kloc 0.34 · lines read 1,003,040 |
| 04.test_growth | test effort kept pace with code written, in the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026)history read the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026) · late test per code 1.706 · early test per code 0.771 |
| 04.fixes_with_tests | fixes usually come with a testfixes 1,191 · share 0.371 · with tests 442 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.dependency_redundancy | one library per job, mostly |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 19 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.correlation_ids | a request can be followed through the logstracing False · request id sites 2 |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 4 |
| 06.alert_rules | alert rules are defined as codealert files 3 |
| 06.deployed_image_floats | every deployed image names a versionimages 11 · floating 0 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.release_markers | releases are markedtags last year 0 · release commits 7 · changelog commits 127 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 322 |
| 03.bus_factor_trend | the team has not narrowed to one person |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 0 · window last 24 months · with tracked 17 |
| 02.ci_presence | CI configuration is present in the working treecount 90 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 3,539 · source 6,045 · test ratio 0.585 |
| 02.conventional_commits | commit subjects generally carry content, in the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026)sampled 49,992 · history read the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026) · low content share 0.0 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 90 · with tests 7 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 7,136 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 90 |
| 02.revert_share | change is rarely undoneshare 0.001 · reverts 16 · recent commits 17,989 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 179 · commits since 6 · days since lockfile changed 0 |
| 02.flaky_test_markers | tests are not retried until they passtest retries 0 · suite retries 0 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 30 · ci configs 90 · product files 2,506 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.014 · commits 17,333 · over 2000 lines 234 |
| 01.burst_import | the largest burst was data and assets (100% 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 it, in the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026)history read the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026) · largest commits b6deeb3..5cb27b1 · bursts explained 24 |
| 01.message_uniformity | commit subjects vary in wording and length, in the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026)history read the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026) · length stdev 14.07 · repeat share 0.005 |
| 01.swallowed_errors | errors are rarely thrown awayloc 1,007,689 · files 17 · per kloc 0.03 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 7 |
| 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 4,855 |
| 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.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.shell_from_strings | product code does not build shell commands from stringssites 1 |
| 05.tls_verification_off | no TLS verification is switched off in product codefiles 0 · sites 0 · pinned instead 0 |
| 05.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 · behind a setting or built here 0 |
| 05.source_maps_shipped | production builds do not publish source mapssites 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.dataset_provenance | little data is committeddata files 0 · licence or card files 0 |
| 05.license_copyleft_inherited | every licence found in vendored code is permissive or weak-copyleftvendored paths 10 |
| 05.license_vendored_unlicensed | all 2 vendored components state their terms, in a licence file, their own headers or a notices filecomponents 2 · stated in headers or notices 2 |
| 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 375 · added in two years 47 · removed within 60 days 2 |
| 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.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.release_branch | the newest release was cut from the branch surveyed, in the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026)elsewhere 0 · on branch 246 · history read the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026) |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 25
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.schema_churn | no schema migrations to read |
| 06.telemetry_depth | none at all is 06.1 |
| 06.print_logging | a frontend: console output is the browser's, not the server's |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 03.active_contributors | not assessed: this check needs the whole history, and only the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026) were read |
| 03.knowledge_silos | not assessed: this check needs the whole history, and only the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026) were read |
| 03.drive_by_contributors | not assessed: this check needs the whole history, and only the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026) were read |
| 03.contributor_attrition | not assessed: this check needs the whole history, and only the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026) were read |
| 02.release_cadence | not assessed: this check needs the whole history, and only the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026) were read |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 01.initial_dump | not assessed: this check needs the whole history, and only the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026) were read |
| 01.revision_depth | not assessed: this check needs the whole history, and only the most recent 50,000 commits (10 Mar 2022 to 22 Oct 2026) were read |
| 01.notebook_outputs | too few notebooks |
| 05.migration_reversibility | too few migrations to judge |
| 05.resource_limits | no Kubernetes workload manifests |
| 05.public_env_secret | not assessed for Kotlin or Python, the languages the product is written in: this check's patterns read other languages only |
| 05.unsafe_html | not assessed for Kotlin or Python, the languages the product is written in: this check's patterns read other languages only |
| 05.cleartext_traffic | not a mobile app |
| 05.license_manifest_conflict | no packaging manifest states a licence |
| 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 PyPI airbyte-destination-pgvector (an empty record for a package published here) did not; NVD: 2 records name airbyte with nothing tying them to this repository (CVE-2026-92203, CVE-2026-92204) |
| 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 AFY2-QRWP-BK8M 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/AFY2QRWPBK8M?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: 928.0authenticated: False |
| 131.2s | cloned the repository to a temporary directory | depth: full |
| 205.6s | read the git history | commits: 50000tracked files: 19368 |
| 646.0s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 646.0s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 820.6s | kept the facts, never the source, for re-reading under new checks | |
| 820.6s | deleting the working copy |
Total 820.6s ·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).