mrkeyoor.comAsk

cordiverse/cordistested 09 Oct 2026commit f8ea3cd

cordis review

Prototype Cordis if dependency-aware activation and reversible registrations solve a concrete problem in your plugin host.

  • Build failed
  • Tests failed
90 sto install
  • 432 packages
Dev Toolsevaluationupdated 01 Nov 2026
+86stars / 7d

Consider Cordis for a prototype that needs plugins to wait for services and undo registrations during teardown. Avoid committing to it if your application requires a stable API. Cordis warns that its API is not yet stable and may change without notice. Our run on October 9, 2026, at commit f8ea3cd recorded a successful install step followed by unsuccessful build and test commands. That run did not establish working plugin reload, teardown, or application deployment.

Verdict

Prototype Cordis if dependency-aware activation and reversible registrations solve a concrete problem in your plugin host. Its documented lifecycle model warrants investigation, but our sandbox did not validate that behavior. Resolve the installation and lockfile workflow, obtain actual test results, and exercise teardown before making an adoption decision. Choose a server framework instead when server application architecture or HTTP handling is the requirement.

We ran it

Lab card: what happened when we ran cordis
Lab card from our sandbox run
Screenshot of cordis (deepseek-harness.github.io/deepseek-harness/reference/cordis-primer)
deepseek-harness.github.io/deepseek-harness/reference/cordis-primer
Install✓ · 90s432 packages · 145 MB
Build✗ · 4s
Tests✗ · 2sran, no count parsed
Known vulns00 critical · 0 high · 0 moderate · 0 low (npm audit)
Repo137 files~11,595 lines of source · 0.4 MB · 1 CI workflows

Answers from our run

Does cordis build from source?

Dependencies installed in 90 seconds (432 packages), and the build failed. We cloned commit f8ea3cd into a clean Debian container with 3 CPUs and no project-specific setup.

Do cordis's tests pass?

No. The project's own test command exited unsuccessfully after 2 seconds, and its output did not expose an individual test count.

Does cordis have known vulnerabilities in its dependencies?

npm audit found none in the dependency tree at the time of our run.

Who should not use cordis?

Teams that require a stable API contract.

What are the alternatives to cordis?

NestJS, Fastify. Prototype Cordis if dependency-aware activation and reversible registrations solve a concrete problem in your plugin host.

Setup2/5The harness recorded install success, but build and test commands stopped at Yarn workspace resolution; the install tail also contains unresolved conflicting output.
Docs3/5The linked primer explains services, injection, events, and disposal, while the repository says official documentation is still under construction.
Community3/5Last push on 2026-09-08 and 9,888 stars.Editor’s note: The supplied primary extracts do not establish contributor breadth, support responsiveness, or adoption sufficiently to assess community.
Maturity2/5The repository explicitly warns that its API is not yet stable and may change without notice; our run supplies no runtime validation.

How we score

Discussed on

  1. hnCordis – DeepSeek Harness Plugin Architecture [pdf]3 points

Who it’s for

Framework authors evaluating dependency-aware plugin activation.
Plugin-host developers who need registrations to be removed when a plugin reloads or stops.
Teams willing to validate lifecycle behavior and accommodate API changes.

Who it’s NOT for

Teams that require a stable API contract.
Developers looking for a finished chatbot application or an HTTP server framework.
Teams requiring evidence of passing tests, runtime reliability, or deployment readiness from this sandbox run.

Setup reality

Our sandbox used lab-node:22 with 3 CPUs and 8 GB of memory. The attached harness records install success with exit code 0 in 90 seconds, build failure with exit code 1 in 4 seconds, and test-command failure with exit code 1 in 2 seconds. These are recorded command outcomes, not evidence that application behavior worked.

The install log needs a separate reading. It contains an ERESOLVE conflict involving Vite and the aliased tsx dependency, followed by package-install output. The supplied tail does not establish the full sequence of installation attempts or which recovery options were used. The harness nevertheless records the overall install step as successful.

The stored parser summaries report 432 dependencies occupying 145 MB and an npm audit total of 0. The raw install tail contains a different package count and a nonzero advisory report. Those outputs have not been reconciled; the stored measurements remain unchanged. Scan coverage is unknown because scannedPackages is absent. The recorded audit total does not establish security.

Both subsequent commands entered Yarn 4.14.1 and stopped because the root workspace package was missing from the lockfile. The supplied record contains no passing-test count or coverage result.

What our run establishes

Our run on October 9, 2026, at commit f8ea3cd recorded a successful install step followed by unsuccessful build and test commands. These observations belong to our sandbox, rather than to a production application or a new execution for this correction.

The harness stores each step's success flag, exit code, elapsed time, timeout flag, and log tail. Install was recorded as successful in 90 seconds; build and test commands exited unsuccessfully in 4 and 2 seconds. Neither command timed out. The build and test tails both show Yarn rejecting the workspace lockfile state before producing compiler diagnostics or test results. A failed test command here does not establish failed assertions.

The MrKeyoor testing methodology explains how recorded command outcomes differ from runtime and security validation. That page supplies provenance context; its current procedure does not establish which methodology version governed this older run.

Installation and audit evidence disagree

The install step's recorded success does not erase its log warnings. The tail includes an ERESOLVE dependency conflict involving Vite and an aliased tsx package, then later package-install output. Without a complete-log reconciliation, we cannot identify the full sequence or claim that an ordinary install completed without intervention.

The attached stored parser summaries report 432 dependencies, 145 MB of dependency footprint, and an npm audit total of 0. The raw install tail reports different package and advisory totals. We preserve the stored values and flag the disagreement instead of substituting the tail's figures. The audit total is a recorded advisory result with unknown scan coverage, not proof that the dependency tree is secure.

Test metrics are null. There is no supported aggregate of passed, failed, or skipped tests, and no basis for describing the parser summaries as exhaustive unique coverage. We did not validate a running plugin host, hot reload, teardown order, workload performance, or deployment.

Why evaluate Cordis despite that boundary?

The linked DeepSeek Harness primer describes Cordis as its vendored plugin framework. It explains a context as a repository of services addressed by stable keys. Plugins declare required services through injection and wait until those services exist. This gives a plugin host a way to express dependencies without manually arranging every activation.

The primer describes registrations as reversible effects that reload and teardown unwind. Its examples include prompt sections, tool schemas, adapters, providers, and listeners. This is documented behavior, not a result demonstrated by our run. The primer also advises giving every registration a disposer and keeping related work in one effect when disposal order matters.

That lifecycle model is the reason to prototype Cordis. Start with a small dependency relationship, remove the providing plugin, and check what happens to the consumer and its registrations. Then exercise failed activation and repeated reload. These are proposed acceptance checks, not tests we completed.

API stability and documentation

Cordis warns that its API is not yet stable and may change without notice. Its repository also says official documentation is under construction and points readers to the primer.

The primer provides concrete explanations of contexts, injection, dispatch modes, and disposal, but it addresses authors working inside DeepSeek Harness. General adopters must distinguish those host-specific examples from the framework behavior they need. Current documentation also cannot prove that every described behavior matches the measured commit.

When a server framework fits better

NestJS is a TypeScript framework for Node.js server-side applications. Consider it when your main decision concerns server application architecture. The supplied extract does not establish an equivalent to Cordis's runtime disposal model.

Fastify is a web framework with hooks, plugins, and decorators. Consider it when HTTP routes and server extensions define the application. Its plugin architecture alone does not establish interchangeable lifecycle behavior with Cordis.

These are alternatives for different application goals, rather than demonstrated replacements for Cordis's teardown behavior. The supplied sources do not establish an integration between them and Cordis.

How to read the scores

Assessed scores use a 1 to 5 editorial rubric: 1 means a demonstrated blocker for the dimension; 2 means substantial unresolved constraints; 3 means useful evidence with material gaps; 4 means strong evidence with limited gaps; 5 means comprehensive evidence within the stated scope. These are judgments about the supplied evidence, not performance measurements. Unassessed means the evidence cannot support a rating.

Setup receives 2 because installation was recorded as successful but subsequent commands stopped at workspace resolution. Documentation receives 3 because the primer explains the model while official documentation remains under construction. Maturity receives 2 because the project explicitly warns of API instability. Community is unassessed: the supplied primary extracts do not establish contributor breadth, support responsiveness, or adoption.

Alternatives

ProjectWhat it isPick it when
NestJS gh↗A TypeScript framework for Node.js server-side applications.Consider it when you need server application architecture; the supplied evidence does not establish equivalent runtime plugin disposal.
Fastify gh↗A web framework extensible through hooks, plugins, and decorators.Consider it when HTTP routes and server extensions are the main requirement; do not assume its plugin lifecycle matches Cordis.

Sources

  1. Cordis README
  2. Cordis repository
  3. Cordis primer in English
  4. Failed fiber reload report #95
  5. Waterfall double-invocation fix #83

More dev tools reviews