fbc6055 · 839 commits · 3,230 files
Issued 2026-10-28
Nothing significant. Questions worth asking about Observability & Operations, Engineering Process & SDLC Maturity.
106 checks ran across 6 assessable dimensions. 1 finding is worth checking first. 9 findings, each with evidence. One dimension cannot be assessed without an acquirer.
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 36 locked dependencies have published vulnerabilities, 37 high or critical in what ships
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | strong | |
| 02 | Engineering Process & SDLC Maturity | adequate | |
| 03 | Organization & Key-Person Risk | adequate | |
| 04 | Product & Engineering Maturity | strong | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 20% 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 ↑packages/sie_server_sidecar/src/dispatcher.rs is 10,552 lines, 55× this codebase's median file
adequateThe median source file here is 190 lines. 36 files exceed 1,900 lines, the largest being 10,552. 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/sie_server_sidecar/src/dispatcher.rs:1 — 10,552 lines (55× median) |
| line-count | packages/sie_gateway/src/queue/publisher.rs:1 — 10,446 lines (54× median) |
| line-count | packages/sie_gateway/src/state/model_registry.rs:1 — 7,858 lines (41× median) |
| line-count | packages/sie_server_rust/src/candle_backend.rs:1 — 7,341 lines (38× median) |
| line-count | packages/sie_gateway/src/handlers/serving_disclosure.rs:1 — 5,781 lines (30× 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 · adequate · ratings ↑9% of recent commits change more than 2,000 lines
adequate59 of 649 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| git log --numstat | 59 commits over 2,000 lines |
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.
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/sie_ts_sdk/playwright.config.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.
| packages/sie_ts_sdk/playwright.config.ts | packages/sie_ts_sdk/playwright.config.ts:22 — 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 · adequate · ratings ↑One person alone changes authentication
adequateIn the last 24 months, of 20 contributors, a single person made every change to: authentication (13 commits). These are the parts where a mistake is expensive and where knowledge is hardest to rebuild. Ask who else could change them safely tomorrow.
| git log -- <area> | sole author over 24 months: authentication (13 commits) |
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 · strong · ratings ↑No finding. 19 checks ran and none fired; the rejection log below says why each did not.
Security & Reliability Posture
05 · adequate · ratings ↑36 locked dependencies have published vulnerabilities, 37 high or critical in what ships
adequate worth checking first36 of 1,878 locked dependencies match 128 published advisories in OSV, 62 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.
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 uv.lock settles it. If it holds when someone checks it, this finding is significant.
| uv.lock | uv.lock — authlib 1.7.2: GHSA-6v38-4h7w-rj9h (critical), fixed in 1.9.0 |
| uv.lock | uv.lock — certifi 2026.4.22: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.18 |
| uv.lock | uv.lock — chromadb 1.5.9: GHSA-36p7-vc44-83pf (critical) |
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.
1 deserialiser that can run code
adequate1 places read data with a deserialiser that executes what it reads (`yaml.load` without a safe loader). 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.
| packages/sie_server/src/sie_server/config/upstreams.py | packages/sie_server/src/sie_server/config/upstreams.py:431 — 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.
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 3,041 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.
Readiness and liveness probes are identical in 2 of 7 workloads
adequateBoth probes call the same endpoint. When a dependency slows down, the liveness probe fails with the readiness probe, so the platform restarts pods that only needed taking out of rotation, and a partial outage becomes a full one. Liveness should ask whether the process is alive; readiness whether it can serve.
| deploy/helm/sie-cluster/templates/mcp-edge-deployment.yaml | deploy/helm/sie-cluster/templates/mcp-edge-deployment.yaml — same probe endpoint twice |
| deploy/helm/sie-cluster/templates/otel-collector.yaml | deploy/helm/sie-cluster/templates/otel-collector.yaml — same probe endpoint twice |
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
5 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 1,132 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 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 Python codebase, with Rust alongside (28% of source files). Does your engineering organisation already run Python in production, or would this be the first?
- The bulk of this system sits in packages/, deploy/, integrations/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (deploy/helm/sie-cluster/.gitignore and 88 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/superlinked/sie/fbc6055)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 — 97 signals that ran and did not fire
Appendix: rejection log — 97 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 — 75
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 2,497 · top5 share 0.039 |
| 04.debt_markers | debt markers are sparsemarkers 7 · per kloc 0.01 · lines read 1,027,898 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.eol_runtime | every pinned runtime is still supportedeol as of 2026-09-24 |
| 04.fixes_with_tests | fixes usually come with a testfixes 306 · share 0.801 · with tests 245 |
| 04.compat_layers | little code is kept for the old wayshare 0.002 · code files 651 · compat files 1 |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 150 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.telemetry_depth | the service is visible in more than one way |
| 06.print_logging | raw prints are few, or outnumbered by logger callsprints 8 · logger calls 931 |
| 06.correlation_ids | a request can be followed through the logstracing True · request id sites 31 |
| 06.alert_rules | alert rules are defined as codealert files 2 |
| 06.deployed_image_floats | every deployed image names a versionimages 5 · floating 0 |
| 06.single_replica | an autoscaler or disruption budget is definedworkloads 7 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.release_markers | releases are markedtags last year 55 · release commits 0 · changelog commits 16 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 0.6 · window last 24 months · authors 20 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 20 · directories 4 |
| 03.drive_by_contributors | a healthy share of contributors committed more than onceshare 0.3 · authors 20 · one commit authors 6 |
| 03.contributor_attrition | the dominant contributor is still activeauthors 20 · top share a quarter or more · top contributor last committed within the last three months |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 89 · window last 24 months · with tracked 4 |
| 02.ci_presence | CI configuration is present in the working treecount 18 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 915 · source 1,405 · test ratio 0.651 |
| 02.release_cadence | tags are presenttags 55 |
| 02.conventional_commits | commit subjects generally carry contentsampled 750 · 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 18 · with tests 1 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 8 · test files 806 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 18 |
| 02.revert_share | change is rarely undoneshare 0.0 · reverts 0 · recent commits 685 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 64 · commits since 6 · days since lockfile changed 0 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 62 · ci configs 18 · product files 651 |
| 02.long_lived_branches | the typical branch reaches the trunk quicklyshare 0.0 · merges 68 · long lived 0 |
| 01.burst_import | no commit run met both the rate and the net-addition thresholdgap seconds 180 · min add ratio 3.0 · min net added 2,000 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 0 · share of insertions 0.0 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 19.93 · repeat share 0.003 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 1,086 · write once share 0.238 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0164 · product files 626 · distinct blocks 253,408 |
| 01.swallowed_errors | errors are rarely thrown awayloc 1,030,851 · files 30 · per kloc 0.07 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 16 |
| 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 3,041 |
| 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_in_history | no credential-shaped string was ever added outside test and fixture pathspatterns 8 · truncated False · added lines 1,382,142 |
| 05.container_runs_as_root | every shipped Dockerfile drops to a non-root user or builds on a non-root base imagedockerfiles 5 |
| 05.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.supply_chain_pinning | third-party build steps are pinned, or fewaction refs 108 · pipe to shell 0 · unpinned third party 0 |
| 05.outbound_timeouts | outbound calls set timeouts, or are fewcalls without timeout 0 |
| 05.sql_from_strings | no SQL is assembled from strings in product codefiles 0 · sites 0 · value interpolated 0 |
| 05.shell_from_strings | product code does not build shell commands from stringssites 0 |
| 05.tls_verification_off | no TLS verification is switched off in product codefiles 0 · sites 0 · pinned instead 0 |
| 05.resource_limits | every workload declares limitsworkloads 8 · without limits 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.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.dataset_provenance | data files carry a licence or carddata files 0 · licence or card files 1 |
| 05.license_copyleft_inherited | every licence found in vendored code is permissive or weak-copyleftvendored paths 40 |
| 05.license_vendored_unlicensed | all 5 vendored components state their terms, in a licence file, their own headers or a notices filecomponents 5 · stated in headers or notices 0 |
| 05.license_grant_unclear | the licence is recognisable as Apache-2.0class permissive · license Apache-2.0 |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.api_versions_coexisting | the newer API version is recent; the old one may be on its way outmonths together 3 |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 0 · files with deprecations 1 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 371 · added in two years 371 · removed within 60 days 4 |
| 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 |
| 05.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 2.5 · days since last tag 14 · commits last 90 days 724 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 0 · on branch 55 · tags in window 55 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 22
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.test_growth | history too short to compare code and test growth |
| 04.churn_trend | history too short to read a churn trend |
| 04.fix_share_trend | fewer than six busy quarters to compare |
| 04.schema_churn | no schema migrations to read |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.usage_reporting_default | the reporting hosts the product's code names are not the project's own |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 03.active_contributors | history too short to distinguish active from historical contributors |
| 03.second_contributor_attrition | too little history |
| 03.bus_factor_trend | fewer than three active years to compare |
| 03.joiners_and_leavers | too few regular contributors to see a trend |
| 01.notebook_outputs | too few notebooks |
| 05.migration_reversibility | too few migrations to judge |
| 05.public_env_secret | not a frontend |
| 05.unsafe_html | not a frontend |
| 05.source_maps_shipped | not a frontend |
| 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 |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; OSV npm @superlinked/sie-chroma (an empty record for a package published here), OSV npm @superlinked/sie-lancedb (an empty record for a package published here), OSV npm @superlinked/sie-langchain (an empty record for a package published here), OSV npm @superlinked/sie-llamaindex (an empty record for a package published here), OSV npm @superlinked/sie-sdk (an empty record for a package published here), NVD did not |
| 05.advisory_record | record incomplete: no advisory against the project in the last 24 months; OSV npm @superlinked/sie-chroma (an empty record for a package published here), OSV npm @superlinked/sie-lancedb (an empty record for a package published here), OSV npm @superlinked/sie-langchain (an empty record for a package published here), OSV npm @superlinked/sie-llamaindex (an empty record for a package published here), OSV npm @superlinked/sie-sdk (an empty record for a package published here), NVD did not answer |
| 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 YYQK-4WB6-W09Q 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/YYQK4WB6W09Q?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: 85.5authenticated: False |
| 7.3s | cloned the repository to a temporary directory | depth: full |
| 10.7s | read the git history | commits: 839tracked files: 3230 |
| 222.4s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 222.4s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 348.0s | kept the facts, never the source, for re-reading under new checks | |
| 348.0s | deleting the working copy |
Total 348.0s ·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).