Docmd Search
mgks · App
docmd-search is an offline semantic search engine for documentation. It discovers the files in a folder, splits them by heading, creates embeddings on your own machine with ONNX Runtime and writes an index you can search in the terminal or load in a browser. You choose one of four embedding models on first run, and no cloud API key is needed. It works with any documentation project and also plugs into docmd as a search plugin.
Written by ooruby from the README of docmd-search 0.1.6.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Documentation search that matches on meaning as well as keywords, with embeddings made on your own machine instead of a cloud service.
What you could do with it
- Point it at a docs folder and search it by meaning from the terminal while indexing continues.
- Build a browser-ready index for your documentation site so readers can search it by meaning.
- Call its programmatic interface from a script or CI pipeline to index a directory of documents.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Offline semantic search engine for documentation. Local embeddings, browser-ready indexes.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.1.6, the file with digest sha512-KrESkYVwKAtKLIdBeM4p+JjkAfkl/rW0fvaa2fNl2MkJzCdhbk/raVv/I4k5YkIUQI1f2+BILb8xCr6LAr61iw==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y docmd-search@0.1.6Pinned to 0.1.6, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- docmd-search
- Version read
- 0.1.6
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/docmd-io/docmd-search
- Commit
- 9ff08eefaf81
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/docmd-search)About this listing
- Kind
- App
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-06
More from mgks
See the storefrontSimilar apps
All appsPuts Claude in your terminal to understand your codebase, edit files and handle git workflows.
Gives your app one API for streaming from many AI model providers, with typed and validated tools.
Estimates how many tokens a text will use without loading a full tokeniser, from code or the shell.
Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.