ssh-mcp-pro 1.2.1 → 1.2.3

package/docs/development/release-process.md

@@ -1,57 +1,31 @@
 # Release Process
 
-## Versioning
-
-Semantic Versioning, automated by [release-please](https://github.com/googleapis/release-please)
-per [release-please-config.json](../../release-please-config.json) (`node` release
-type). Conventional Commit types on `main` (see
-[commit-conventions.md](commit-conventions.md)) drive whether the next release is a
-patch, minor, or major bump.
-
-## How a release happens
-
-1. Conventional commits land on `main`.
-2. The `release` job in [.github/workflows/release.yml](../../.github/workflows/release.yml)
-   runs `googleapis/release-please-action`, which opens or updates a release PR
-   (updating `CHANGELOG.md`, `.release-please-manifest.json`, and the version fields
-   release-please is configured to touch — see `extra-files` in
-   `release-please-config.json`, which includes `mcp.json`, `server.json`, and the MCP
-   registry record).
-3. Merging that PR triggers `release_created`, which runs the `release-assets` job:
-   - `pnpm run check` (full quality gate) must pass.
-   - `pnpm run sbom` generates a CycloneDX SBOM.
-   - The package is packed with `pnpm pack`, and both the tarball and the SBOM get a
-     `sha256sum` checksum file.
-   - `actions/attest-build-provenance` runs twice — once for the package, once for the
-     SBOM — producing verifiable build provenance attestations.
-   - All artifacts (tarball, SBOM, checksums) are attached to the GitHub Release.
-   - npm publish only happens if the repository variable `AUTO_RELEASE_PUBLISH` is
-     `"true"`; otherwise the step is a documented no-op ("npm publishing is disabled by
-     AUTO_RELEASE_PUBLISH").
-
-## Verifying a release artifact
-
-```bash
-sha256sum -c ssh-mcp-pro-<version>.tgz.sha256
-```
-
-For provenance, use [GitHub CLI attestation verification](https://cli.github.com/manual/gh_attestation_verify):
-
-```bash
-gh attestation verify ssh-mcp-pro-<version>.tgz --owner oaslananka
-```
-
-See [docs/security/release-integrity.md](../security/release-integrity.md) for the full
-supply-chain rationale.
-
-## Current status
-
-No release has been published yet (repository created 2026-06-28). Release PR #1
-(`chore(main): release ssh-mcp-pro 1.2.0`) is open and is the first opportunity to
-exercise this pipeline end-to-end — see [ROADMAP.md](../../ROADMAP.md).
-
-## Container images
-
-Published separately by [.github/workflows/docker.yml](../../.github/workflows/docker.yml)
-on tagged releases; see [docs/docker.md](../docker.md) for tag policy and digest-pinned
-usage.
+## Prepare a version
+
+Release Please v5 prepares Conventional Commit-driven version updates on `main`. A release PR updates `CHANGELOG.md`, package, registry metadata, client readiness metadata and embedded version strings together. Merge a release PR only after the normal protected-branch checks pass.
+
+When an unreleased version reaches `main`, the `Release` workflow preflights the **frozen dependency installation, full quality check, dependency freshness, package build, SBOM, checksums and GitHub artifact attestations** before Release Please creates the tag. It then attaches that exact prebuilt package and SBOM to the GitHub Release and dispatches an immutable-tag GHCR build. Ordinary main pushes without a new version do not repeat the heavy preflight.
+
+## One-click npm publication
+
+**Actions → Release → Run workflow → main → Run workflow** is the **manual npm publish button**. No extra version input, stage job or automatic npm publish on release PR merge is involved.
+
+The `Publish current GitHub Release to npm` job identifies the `package.json` version on `main`, locates its immutable GitHub Release, downloads the already-built `.tgz` and checksum, verifies the tag's source/version, checks SHA-256, package metadata and the GitHub attestation, then calls **`npm publish` directly with GitHub-hosted Actions OIDC**. A version already public on npm is not published twice. After confirming that exact npm version is public, it dispatches the matching MCP Registry publication job. npm Trusted Publisher must authorize `.github/workflows/release.yml` and permit **direct publication**, not stage-only. This is a provider-side prerequisite, not a second GitHub workflow.
+
+GitHub does not override npm account/package security settings. If the npm publisher is configured for stage-only access or another mandatory owner restriction, the direct publish job fails clearly instead of silently staging or bypassing security. Avoid publishing historical versions to work around an npm account restriction; repair the publisher configuration through authorized account settings.
+
+## GHCR and MCP Registry
+
+The release workflow triggers `.github/workflows/docker.yml` with the immutable `ssh-mcp-pro-vX.Y.Z` tag. GHCR must grant this repository's GitHub Actions **Write** access to the existing `ghcr.io/oaslananka/ssh-mcp-pro` package. Package access is managed through **GitHub Packages → Package settings → Manage Actions access**. Docker publishing verifies the release tag and package version before pushing both platform tags.
+
+The MCP Registry job requires an existing GitHub Release and the *same publicly visible npm version*. It skips versions already registered and uses GitHub OIDC. There is no daily staged-publication reconciliation job. The manual npm publish workflow dispatches the MCP Registry publication only after npm confirms the version is public.
+
+## Verify and troubleshoot
+
+- `gh release view ssh-mcp-pro-vX.Y.Z --json assets` — the prepared GitHub Release.
+- `gh run list --workflow release.yml` — release preparation and manual npm publication status.
+- `npm view ssh-mcp-pro@X.Y.Z version` — independently verify actual npm publication.
+- `gh run list --workflow docker.yml` and `gh api users/oaslananka/packages/container/ssh-mcp-pro` — GHCR status.
+- `gh run list --workflow publish-mcp-registry.yml` — MCP Registry publication.
+
+Do not confuse a successful GitHub Release (or npm production environment deployment event) with a successful public npm/GHCR publication. Check the actual registry records before announcing an ecosystem release.

package/docs/remote-mcp-hardening.md

@@ -21,6 +21,23 @@ Use this checklist before exposing `ssh-mcp-pro` through a public Streamable HTT
 
 ## OAuth and token verification
 
+The remote control plane requires explicit browser confirmation before redirecting
+users to GitHub OAuth. `/oauth/authorize` shows the client destination and scopes;
+a same-browser, short-lived HttpOnly/SameSite transaction cookie is required by
+`POST /oauth/approve` and the GitHub callback. Real HTTPS deployments add `Secure`.
+Clients must keep PKCE and exact registered redirect URI matching. Public dynamic
+client registrations are limited to 20 per TCP peer per five minutes per process,
+with the existing global database cap retained. Deployments behind shared proxies
+should also enforce edge rate limits and monitor registration exhaustion.
+
+Remote REST endpoints enforce OAuth token capabilities independently: agent list
+and details require `agents:read`; audit history requires `agents:admin`.
+
+Remote agent file writes use verified same-directory temporary files and atomic
+replacement so an interrupted write does not truncate an existing target. Renaming
+requires write permission on the containing directory, in addition to file access.
+
+
 - Prefer OAuth mode for public endpoints.
 - Configure `SSH_MCP_OAUTH_ISSUER`, `SSH_MCP_OAUTH_JWKS_URL`, and either `SSH_MCP_OAUTH_AUDIENCE` or `SSH_MCP_OAUTH_RESOURCE` explicitly.
 - Use `SSH_MCP_OAUTH_ALLOWED_ALGORITHMS` to pin accepted JWT algorithms when your authorization server has a stable signing policy.

package/mcp.json

@@ -2,7 +2,7 @@
   "name": "ssh-mcp-pro",
   "display_name": "ssh-mcp-pro",
   "description": "Secure MCP SSH automation server with policy controls, resources, prompts, stdio, and HTTP.",
-  "version": "1.2.1",
+  "version": "1.2.3",
   "author": "Osman Aslan",
   "license": "MIT",
   "runtime": "node",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ssh-mcp-pro",
-  "version": "1.2.1",
+  "version": "1.2.3",
   "mcpName": "io.github.oaslananka/ssh-mcp-pro",
   "description": "Model Context Protocol (MCP) SSH client server for remote automation",
   "type": "module",
@@ -67,6 +67,7 @@
     "@opentelemetry/resources": "^2.11.0",
     "@opentelemetry/sdk-node": "^0.222.0",
     "@opentelemetry/semantic-conventions": "^1.43.0",
+    "html-escaper": "3.0.3",
     "jose": "6.2.3",
     "node-ssh": "^13.2.1",
     "ws": "^8.21.1",
@@ -76,6 +77,7 @@
     "@stryker-mutator/core": "9.6.1",
     "@stryker-mutator/typescript-checker": "9.6.1",
     "@stryker-mutator/vitest-runner": "9.6.1",
+    "@types/html-escaper": "3.0.4",
     "@types/node": "^24.13.1",
     "@types/ssh2": "^1.15.6",
     "@types/ws": "^8.18.2",
@@ -101,7 +103,7 @@
     "ip-address": "^10.7.1",
     "nanoid": "^3.3.18",
     "browserslist": "^4.28.7",
-    "@hono/node-server": "^2.0.5",
+    "@hono/node-server": "^2.1.3",
     "markdown-it": "^14.3.2",
     "vitest": "^4.1.11"
   },
@@ -159,8 +161,8 @@
     "pack:check": "node scripts/check-package-contents.mjs",
     "pack:install-smoke": "node scripts/check-package-install-smoke.mjs",
     "pack:lint": "publint --strict=false",
-    "check:knip": "knip -c knip.jsonc --reporter compact || true",
-    "check:circular": "depcruise src --config .dependency-cruiser.mjs || true",
+    "check:knip": "knip -c knip.jsonc --include files,dependencies,unlisted,unresolved,cycles --reporter compact",
+    "check:circular": "depcruise src --config .dependency-cruiser.mjs",
     "check:module-size": "node scripts/check-module-size.mjs",
     "check:maintainability": "pnpm run check:module-size && pnpm run check:circular && pnpm run check:knip",
     "check:quality": "pnpm run format:check && pnpm run check:doc-language && pnpm run check:package-scripts && pnpm run check:rulesets && pnpm run verify:actions-runtime && pnpm run lint && pnpm run typecheck && pnpm run audit && pnpm run licenses:check",

package/registry/ssh-mcp-pro/mcp.json

@@ -2,7 +2,7 @@
   "name": "ssh-mcp-pro",
   "display_name": "ssh-mcp-pro",
   "description": "Secure MCP SSH automation server with policy controls, resources, prompts, stdio, and HTTP.",
-  "version": "1.2.1",
+  "version": "1.2.3",
   "author": "Osman Aslan",
   "license": "MIT",
   "runtime": "node",

package/server.json

@@ -7,13 +7,13 @@
     "url": "https://github.com/oaslananka/ssh-mcp-pro",
     "source": "github"
   },
-  "version": "1.2.1",
+  "version": "1.2.3",
   "packages": [
     {
       "registryType": "npm",
       "registryBaseUrl": "https://registry.npmjs.org",
       "identifier": "ssh-mcp-pro",
-      "version": "1.2.1",
+      "version": "1.2.3",
       "transport": {
         "type": "stdio"
       }
@@ -22,7 +22,7 @@
       "registryType": "npm",
       "registryBaseUrl": "https://registry.npmjs.org",
       "identifier": "ssh-mcp-pro",
-      "version": "1.2.1",
+      "version": "1.2.3",
       "runtimeHint": "npx",
       "transport": {
         "type": "streamable-http",