ssh ai chat - Moses Yebei

tagged reasoning content. A typical workflow: user SSHs in, verifyPublicKey checks their GitHub key against the whitelist/blacklist, useChat establishes the session, messages flow through appendMessage and are stored via createOrUpdateConversation`, and the AI response streams back through the same path.

Code Health & Issues

HIGH - Pin third-party GitHub Actions to a commit SHA - .github/workflows: docker/setup-qemu-action@v3, docker/setup-buildx-action@v3, docker/login-action@v3, docker/metadata-action@v5 are on mutable tags, risking supply chain compromise.
HIGH - Add a test suite; this repository has none: 46 source files with zero test files means any change ships with no signal existing behavior holds.
MEDIUM - Enable Dependabot or Renovate: 1 manifest(s) with no update bot configured; advisories remain unpatched without automated monitoring.
MEDIUM - Pin the container base image by digest - Dockerfile: node:22-slim and gcr.io/distroless/nodejs22-debian12 use mutable tags, meaning build composition can change between runs without record.
MEDIUM - Gate pull requests on a dependency vulnerability scan - .github/workflows: no dependency scan in CI; a known-vulnerable package could reach production undetected.
MEDIUM - Add a non-root USER to the image - Dockerfile: CMD/ENTRYPOINT with no USER directive; process runs as root against every mounted volume.
MEDIUM - Review the install lifecycle script and disable scripts in CI - package.json: postinstall script executes during install, creating an event-stream-style compromise vector in CI.
LOW - Set timeout-minutes on the workflow jobs - .github/workflows/docker.yml: 1 workflow declares no job timeout; a wedged step runs to the six-hour platform default.
LOW - Add the repository convention files this project lacks: missing .editorconfig, .gitattributes with text=auto eol=lf, and a formatter config.

The Bottom Line

This is a functional SSH AI chat implementation with a clean separation between auth, chat state, and data access. The codebase is well-structured for its scope, with clear entry points and a resolvable call graph. However, the absence of tests and the use of mutable GitHub Action tags and base images represent real production risks. Teams comfortable with SSH-based tooling and who accept the current health trade-offs can deploy this, but anyone requiring auditability or long-term maintainability should address the high-severity findings first.

What the analyser found

Deployment readiness

6/7

Container image
CI pipeline
Lockfile committed
Test suite
README
License
No committed secrets

Composition

80 files

TypeScript28
TSX16
JSON10
YAML6
Markdown5
SQL1

ReactDocker

Module dependencies

The 10 most depended-upon modules of 46, from static import analysis. Red outline marks a module in an import cycle.

graph LR n0_src_db_schema["schema"] n1_src_app_index["index"] n2_src_db_index["index"] n3_src_server["server"] n4_src_components_chat_messages["messages"] n5_src_ai_config["config"] n6_src_app_chat["chat"] n7_src_app_help["help"] n8_src_app_language["language"] n9_src_auth_index["index"] n1_src_app_index --> n6_src_app_chat n1_src_app_index --> n7_src_app_help n1_src_app_index --> n8_src_app_language n2_src_db_index --> n0_src_db_schema n3_src_server --> n1_src_app_index n3_src_server --> n9_src_auth_index

Findings

MediumNo test files detected - untested code paths repository-wide

What would stop me shipping this

Ranked by severity × confidence × production reach. Reach is the honest discriminator across a collection that is mostly other people's code: the same finding matters more in something that ships.

high2

medium5

low2

Pin third-party GitHub Actions to a commit SHAhigh5 occurrences

.github/workflows

docker/setup-qemu-action@v3, docker/setup-buildx-action@v3, docker/login-action@v3, docker/metadata-action@v5

A tag can be moved, so the action running with your token and secrets is whatever its owner last pushed; this is how tj-actions/changed-files leaked secrets from thousands of repos.

Fix: Replace each @vN with the 40-character commit SHA, keep # vN as a comment, and let Dependabot bump the SHAs.

Add a test suite; this repository has nonehigh46 occurrences

46 source files, no test files

Any change ships with no signal that existing behaviour still holds, so a regression reaches production undetected.

Fix: Add one test per public entry point, then a CI step that runs them.

Enable Dependabot or Renovatemedium

1 manifest(s), no update bot configured

Without a bot a published advisory sits unpatched until someone audits by hand, which across 1,322 repositories means never.

Fix: Commit .github/dependabot.yml covering the repo ecosystems plus github-actions.

Pin the container base image by digestmedium2 occurrences

Dockerfile

node:22-slim, gcr.io/distroless/nodejs22-debian12 (mutable tag)

An untagged or mutable base means today's build and last month's contain different libc and a different CVE set, with no record of which shipped.

Fix: Use image:tag@sha256:<digest> and enable Dependabot's docker ecosystem.

Gate pull requests on a dependency vulnerability scanmedium

.github/workflows

no dependency scan in CI

This is the one gate that would catch a known-vulnerable package before it reaches a build, and no repository in the sample had it.

Fix: Add dependency-review-action on pull_request, or osv-scanner on push and a schedule.

Add a non-root USER to the imagemedium

Dockerfile

CMD or ENTRYPOINT with no USER directive

A process running as root in the container is root against every mounted volume, and it turns any container escape or writable-mount mistake from a contained problem into a host one.

Fix: Create an unprivileged user, chown what it needs, and end the Dockerfile with USER.

Review the install lifecycle script and disable scripts in CImedium

package.json

postinstall

Install scripts are the execution vector for every npm compromise from event-stream onward, and a postinstall that fetches a binary makes the build depend on a URL nobody reviews.

Fix: Move the work into an explicit build step, or set ignore-scripts in CI and run it by name.

Set timeout-minutes on the workflow jobslow

.github/workflows/docker.yml

1 workflow(s) declare no job timeout

A wedged step runs to the six-hour platform default, which on a two-hourly schedule means three runs overlap behind it.

Fix: Add timeout-minutes with a realistic bound to each job.

Add the repository convention files this project lackslow3 occurrences

missing .editorconfig, .gitattributes, a formatter config

Without them one contributor's editor writes tabs into a Python file, a shell script commits with CRLF and fails in the container, and a notebook diff is unreviewable.

Fix: Add .editorconfig, .gitattributes with text=auto eol=lf, and a formatter config.

Checked deterministically against the repository tree and a bounded set of its files: committed credentials, unpinned actions and base images, missing lockfiles and update bots, workflows that discard failures, published advisories against the declared dependencies, runtime configuration, licensing and notebook reproducibility. No language model is involved in this section.