Skip to content

nimo-check v1.0.1

Latest

Choose a tag to compare

@marvtub marvtub released this 28 Oct 01:18
bc0e53e

nimo-check v1.0.1

A GitHub-source CLI and GitHub Action patch for reliable MCP replies, bounded
checks and safer automation output.

Fixes

  • Read correlated MCP results from JSON and server-sent events (SSE), including
    fragmented UTF-8 replies and streams that stay open after the result arrives.
  • Reject unrelated response IDs and ambiguous RPC envelopes instead of using
    another request's result.
  • Enforce the overall timeout across initial requests, response bodies and polling,
    including timers that wake early; reject non-finite timeout values.
  • Validate result fields and finite numeric metrics before writing Action outputs.
  • Keep remote text inert in runner logs, preserve parsed JSON values, escape
    report text in summaries and redact known private check handles across channels.
  • Retain and extend faithful loopback-only protocol, timeout and runner-security
    regression tests when combining the fixes.

Upgrade explicitly

CLI: npx github:marvtub/nimo-mcp#v1.0.1 <url>.

GitHub Action: uses: marvtub/nimo-mcp@v1.0.1.

Existing v1 and v1.0.0 tags are not moved. Existing @v1 users must update their
workflows to opt in. The unversioned GitHub CLI path follows main, subject to local
caching. Use the full release commit SHA for an immutable code selection; a version
tag alone is not an attestation or a claim of GitHub-enforced immutability.

Verification and scope

The release PR candidate passed all 204 committed tests and full CI commands on
Node 18.20.8, 20.20.2, 22.23.1 and 24.15.0. Independent SSE 47-case and actual Action
shell/security 60-case suites passed on Node 18 and 24. Offline packing produced a
four-file archive; its extracted CLI passed the same 47/60 suites as direct Node
invocations plus 10 extra CLI cases on both versions, including real polling,
private-handle redaction, thresholds, keep-open SSE and failure exits.

Known limits remain: some Markdown renderers autolink email text; completed jobs
without evidence can yield null metrics; an output-file failure can follow an
already printed result. Those older five assertions remain recorded failures, not
claimed fixes. Synthetic fixtures are not evidence of successful live-site checks.

This is not an npm publication, hosted-service deployment or MCP Registry update.
server.json remains remote-MCP version 1.0.0. The Action needs Node on the consumer
runner. The merged source also passed a new main-branch CI run with 204/204 tests;
the unchanged packed CLI passed its post-merge 10-case smoke test.

Source and download checksums

Source commit: bc0e53eba6f4e238b47c44842e80660d8819bb8c.

New annotated, unsigned v1.0.1 tag object:
70b150bc66e70bc90f48eb4b17995baee9f65474.

SHA256 for nimo-check-1.0.1.tgz:
971d38e00f28210fdc439faf35614d14462b1bd2c0ccd632e95da489928984ea.

SHA256 for the extracted bin/nimo-check.mjs:
857e401b70ec91729d851b3b1eb03e995d8f0dafc6821daf4efab3a47bf36ab7.

The attached SHA256SUMS verifies the archive by filename. This is the tested
four-file CLI archive; the GitHub Action uses the full tagged repository instead.