6cc1a4a · 11,026 commits · 24,529 files
Issued 2026-10-22
Nothing significant. Questions worth asking about Security & Reliability Posture, Observability & Operations.
103 checks ran across 6 assessable dimensions. 1 finding is worth checking first. 14 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- The project does not take pull requests CONTRIBUTING.md:314
- states a policy on AI-generated contributions AGENTS.md:37
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.20 17 SQL statements built from strings
- 3 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 | 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 |
- 16% 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/core/types/src/order/service.ts is 5,133 lines, 135× this codebase's median file
adequateThe median source file here is 38 lines. 58 files exceed 1,000 lines, the largest being 5,133. 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/core/types/src/order/service.ts:1 — 5,133 lines (135× median) |
| line-count | packages/modules/order/src/services/order-module-service.ts:1 — 4,510 lines (118× median) |
| line-count | packages/modules/product/src/services/product-module-service.ts:1 — 4,281 lines (112× median) |
| line-count | packages/core/types/src/order/common.ts:1 — 3,144 lines (82× median) |
| line-count | packages/core/types/src/fulfillment/service.ts:1 — 3,077 lines (80× 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
adequate310 of 3509 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 | 310 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.
Organization & Key-Person Risk
03 · adequate · ratings ↑The bus factor fell from 4 to 1
adequateYear by year, newest first, the number of people who wrote half the changes was 1, 2, 4, 3. The team narrowed to one person, which is a different risk from one that always was: the code does not say why.
| bus factor by year | 1, 2, 4, 3 |
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 ↑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.
| packages/medusa/src/types/global.ts | packages/medusa/src/types/global.ts — deprecated since Mar 2024 |
| packages/core/types/src/common/config-module.ts | packages/core/types/src/common/config-module.ts — deprecated since May 2024 |
| packages/core/utils/src/modules-sdk/types/medusa-service.ts | packages/core/utils/src/modules-sdk/types/medusa-service.ts — deprecated since Jul 2024 |
| packages/core/utils/src/modules-sdk/joiner-config-builder.ts | packages/core/utils/src/modules-sdk/joiner-config-builder.ts — deprecated since Jul 2024 |
| packages/core/utils/src/common/define-config.ts | packages/core/utils/src/common/define-config.ts — deprecated since Oct 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 ↑1 Dockerfile runs 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 | .oss-scanner/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.
17 SQL statements built from strings
adequate worth checking first17 places in product code build SQL by formatting or joining strings rather than passing parameters, and in 5 of them a value, not a table or column name, goes into the string. Where any of those values comes from a request, it is an injection point. Each site needs a look; the fix, parameters, is small.
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 packages/cli/create-medusa-app/src/utils/create-db.ts:27 and the 2 other files it cites settles it. If it holds when someone checks it, this finding is significant.
| packages/cli/create-medusa-app/src/utils/create-db.ts | packages/cli/create-medusa-app/src/utils/create-db.ts:27 — SQL built from a string |
| packages/core/utils/src/pg/index.ts | packages/core/utils/src/pg/index.ts:48 — SQL built from a string |
| packages/modules/product/src/repositories/product.ts | packages/modules/product/src/repositories/product.ts:435 — 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.
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.
| packages/design-system/icons/rollup.config.mjs | packages/design-system/icons/rollup.config.mjs:19 — 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.
The build runs third-party code it does not pin
adequate9 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/action.yml | .github/workflows/action.yml:25 — action pinned by tag |
| .github/workflows/action.yml | .github/workflows/action.yml:168 — 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.
3 shell commands built from strings
adequate3 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.
| packages/medusa/src/commands/develop.ts | packages/medusa/src/commands/develop.ts:185 — command run through a shell |
| www/utils/packages/docs-automator/src/classes/diff-analyzer.ts | www/utils/packages/docs-automator/src/classes/diff-analyzer.ts:73 — command run through a shell |
| www/utils/packages/docs-automator/src/classes/diff-analyzer.ts | www/utils/packages/docs-automator/src/classes/diff-analyzer.ts:149 — 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.
86 locked dependencies have published vulnerabilities, 94 high or critical
adequate86 of 3,863 locked dependencies match 176 published advisories in OSV, 94 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.
| www/yarn.lock | www/yarn.lock — dompurify 3.4.15: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17 |
| yarn.lock | yarn.lock — dompurify 3.4.16: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17 |
| www/utils/yarn.lock | www/utils/yarn.lock — handlebars 4.7.8: GHSA-2w6w-674q-4c4q (critical), fixed in 4.7.9 |
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.
4 vendored components with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| packages/deps/AGENTS.md | packages/deps/AGENTS.md — 1 tracked files, no licence file |
| packages/deps/CHANGELOG.md | packages/deps/CHANGELOG.md — 1 tracked files, no licence file |
| packages/deps/CLAUDE.md | packages/deps/CLAUDE.md — 1 tracked files, no licence file |
| packages/deps/tsconfig.json | packages/deps/tsconfig.json — 1 tracked files, no licence file |
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, 1 high or critical
adequateThe newest was published on 2026-02-11. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version. The record is incomplete: NVD: 2 records name medusa with nothing tying them to this repository (CVE-2023-50258, CVE-2023-50259).
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-2025-69871 | 2026-02-11: CVE-2025-69871 (high): A race condition vulnerability exists in MedusaJS Medusa v2.12.2 and earlier in the registerUsage() function of the promotion module. The function performs a no |
| MAL-2025-191457 | 2025-11-24: MAL-2025-191457 (unrated): Malicious code in @medusajs/medusa (npm) |
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 ↑Sends usage data to telemetry.medusa-commerce.com by default
adequatepackages/medusa-telemetry/src/util/telemetry-dispatcher.js sends to telemetry.medusa-commerce.com, and packages/medusa-telemetry/src/index.js leaves reporting on as shipped. Every installation reports to the vendor unless its operator turns this off. For a buyer running it inside their own product, that is an outbound data flow to a third party: ask what is sent, how often, and whether the buyer's customers were told.
| packages/medusa-telemetry/src/util/telemetry-dispatcher.js | packages/medusa-telemetry/src/util/telemetry-dispatcher.js:16 — reports to telemetry.medusa-commerce.com |
| packages/medusa-telemetry/src/index.js | packages/medusa-telemetry/src/index.js:16 — the reporting setting is on by default |
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 code branches on the environment's name at 22 places
adequate22 places outside configuration test whether they are running in production or staging. Staging then does not exercise production's code, and each deploy is the first run of those branches. Differences belong in configuration the code reads, not in the code.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| packages/cli/medusa-cli/cli.js | packages/cli/medusa-cli/cli.js:7 — branch on the environment name |
| packages/cli/medusa-cli/cli.js | packages/cli/medusa-cli/cli.js:8 — branch on the environment name |
| packages/core/framework/src/http/express-loader.ts | packages/core/framework/src/http/express-loader.ts:32 — branch on the environment name |
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
6 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 19,354 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 589 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 A threat model is in the tree (.oss-scanner/threat_model.md). Does it name the assets this code actually handles, and is it current against the deployment?
- 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 www/, packages/, thoughts/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (.oss-scanner/Dockerfile). 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/medusajs/medusa/6cc1a4a)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 — 89 signals that ran and did not fire
Appendix: rejection log — 89 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 — 72
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 76,256 · top5 share 0.008 |
| 04.debt_markers | debt markers are sparsemarkers 469 · per kloc 0.39 · lines read 1,200,156 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.385 · early test per code 0.461 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.584 · early delete per insert 0.306 |
| 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,652 · share 0.335 · with tests 553 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 9,522 · compat files 1 |
| 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 84 |
| 06.structured_logging | a structured logging library is referencedmatches 4 |
| 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 11 |
| 06.error_reporting | an error reporter is initialisedinitialised 0 · config files 9 |
| 06.release_markers | releases are markedtags last year 2,321 · release commits 0 · changelog commits 24 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 6.8 · window last 24 months · authors 589 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 589 · active 12mo 216 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 589 · directories 4 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 589 · one off share 0.667 |
| 03.contributor_attrition | the dominant contributor is still activeauthors 589 · top share a quarter or more · top contributor last committed within the last three months |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 340 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.joiners_and_leavers | the team is not shrinkingleft 10 · joined 24 · regular last year 39 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 19 · window last 24 months · with tracked 183 |
| 02.ci_presence | CI configuration is present in the working treecount 48 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 2,881 · source 11,227 · test ratio 0.257 |
| 02.release_cadence | tags are presenttags 14,928 |
| 02.conventional_commits | commit subjects generally carry contentsampled 10,626 · low content share 0.011 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 48 · with tests 3 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 4,868 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 48 |
| 02.revert_share | change is rarely undoneshare 0.002 · reverts 8 · recent commits 3,841 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 3 · commits since 15 · days since lockfile changed 1 |
| 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 24 · ci configs 48 · product files 9,522 |
| 01.burst_import | the largest burst was documentation and notebooks (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 itlargest commits 6e7438a..6470168 · bursts explained 4 · largest net added 37,595 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 2 · share of insertions 0.0 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 20.81 · repeat share 0.051 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 16,758 · write once share 0.477 |
| 01.swallowed_errors | errors are rarely thrown awayloc 1,210,345 · files 5 · per kloc 0.0 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 1 |
| 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 13,642 |
| 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.migration_reversibility | migrations can be rolled backshare 0.0 · migrations 226 · irreversible 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 1 |
| 05.unsafe_html | raw HTML is rare, literal or sanitisedsites 2 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.license_copyleft_inherited | every licence found in vendored code is permissive or weak-copyleftvendored paths 33 |
| 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.flags_accumulating | flags are retired about as fast as they are addedlive 10 · retired 7 · flags seen 17 |
| 04.api_versions_coexisting | one API version is served, or none |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 322 · added in two years 126 · removed within 60 days 7 |
| 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 |
| 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 7.0 · days since last tag 1 · commits last 90 days 539 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 41 · on branch 231 · tags in window 272 |
| 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 | columns, once added, stay |
| 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.deployed_image_floats | no deployment descriptor names an image |
| 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.secrets_in_history | no credential-shaped string was added outside test and fixture paths in the 5,902 most recent commits scanned; older history was not read; the only other matches are expired or licence tokens or placeholders, which grant nothing |
| 05.outbound_timeouts | not assessed for TypeScript, the language 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_manifest_conflict | no packaging manifest states a licence |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; OSV npm @medusajs/deps (an empty record for a package published here), OSV npm @medusajs/eslint-plugin (an empty record for a package published here), OSV npm @medusajs/telemetry (an empty record for a package published here), OSV npm @medusajs/test-utils (an empty record for a package published here), OSV npm @medusajs/admin-bundler (an empty record for a package published here), OSV npm @medusajs/admin-sdk (an empty record for a package published here), OSV npm @medusajs/admin-shared (an empty record for a package published here), OSV npm @medusajs/admin-vite-plugin (an empty record for a package published here), OSV npm @medusajs/dashboard (an empty record for a package published here), OSV npm create-medusa-app (an empty record for a package published here), OSV npm @medusajs/http-types-generator (an empty record for a package published here), OSV npm @medusajs/cli (an empty record for a package published here), OSV npm @medusajs/core-flows (an empty record for a package published here), OSV npm @medusajs/framework (an empty record for a package published here), OSV npm @medusajs/instantsearch-adapter (an empty record for a package published here), OSV npm @medusajs/js-sdk (an empty record for a package published here), OSV npm @medusajs/modules-sdk (an empty record for a package published here), OSV npm @medusajs/orchestration (an empty record for a package published here), OSV npm @medusajs/query (an empty record for a package published here), OSV npm @medusajs/types (an empty record for a package published here), OSV npm @medusajs/utils (an empty record for a package published here), OSV npm @medusajs/workflows-sdk (an empty record for a package published here), OSV npm @medusajs/icons (an empty record for a package published here), OSV npm @medusajs/ui-preset (an empty record for a package published here) did not; NVD: 2 records name medusa with nothing tying them to this repository (CVE-2023-50258, CVE-2023-50259) |
| 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 JX5F-ABN6-XX1Z 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/JX5FABN6XX1Z?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: 871.3authenticated: False |
| 109.1s | cloned the repository to a temporary directory | depth: full |
| 352.6s | read the git history | commits: 11026tracked files: 24529 |
| 1111.5s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 1111.5s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 1716.0s | kept the facts, never the source, for re-reading under new checks | |
| 1716.0s | deleting the working copy |
Total 1716.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).