9Router GitHub: find the right source

The upstream 9Router repository is decolua/9router on GitHub. Use that owner and project name to check installation instructions, source changes, and issue reports. A repository with a similar name or copied README is not automatically the same project. This Wiki is independently maintained and does not distribute a modified 9Router build.

Which link should I use?

What you need	Where to look	What to check
Install instructions	Upstream README	npm, Docker, and source are different paths
Published CLI package	npm link from the README	Package name, version, repository field
A fixed bug	Release notes and linked commits	Whether the fix reached your installed build
An existing failure	Issues search	Same version, provider, platform, and error
Inspect a change	GitHub file history	Exact revision, rather than a moving branch

Start at the official repository. Follow its links to packages and container images instead of selecting a lookalike from search. The code being public lets you inspect it; it does not establish that every dependency or configuration is safe for your use.

Package installation or source checkout?

The npm distribution is the shorter path for someone who wants to run the router. A source checkout is useful when you need to inspect or change code, reproduce a patch, or run the development server. The repository’s application package and published CLI package are different artifacts. Running npm install in a checkout installs that checkout’s dependencies; it does not perform the same operation as npm install -g 9router.

Read the installation guide before choosing. If you need source, the upstream command starts with:

git clone https://github.com/decolua/9router.git
cd 9router

Then follow the README associated with your chosen revision for environment configuration, dependencies, build, and startup. Do not combine a Docker volume path from one release with a source-start command from another tutorial.

Record a reproducible version

For a source checkout, record the commit before investigating a bug:

git rev-parse HEAD
git status --short

For a global npm installation, inspect the installed package:

npm list -g 9router --depth=0
npm view 9router version repository.url

The installed and registry versions may differ. A commit merged into the repository can also precede a package release. When somebody says “fixed on main,” check which artifact contains the fix before expecting a package reinstall to change the result.

How to report a useful issue

Search the exact error first. If your failure is new, provide the installed version, operating system, installation method, client name, provider type, and the smallest request that reproduces it. Say whether the dashboard opens, the model list responds, and a direct request to the same provider works.

Remove authorization headers, cookies, account emails, full prompts containing private files, and exported configuration secrets. Keep the error code and nonsecret model identifier. A useful report might say: “The model list succeeds, but this minimal streaming request returns 400 after upgrading from version A to B.” That separates a translation problem from a server that never started.

Should I install from a fork to get a fix?

Only after checking what changed and who maintains that fork. A fork may contain a focused patch, unrelated modifications, or a stale copy of upstream. Compare the relevant commit and installation instructions. Keep your existing data and configuration backed up before trying another build, and use a separate test instance when possible.

GitHub stars and a familiar logo do not prove a binary’s origin. For routine operation, keep the source, package, container, and update instructions tied to the same project. If you only need a working server, continue with 9Router installation; if the installed executable cannot be found, use the npm environment guide.