DEDUPED Hot AI repos, turned into use cases Get 5 a day

What you can do with Jevcore

jevcore is a TypeScript package that gives DeepSeek Harness, MCP hosts, and plain Node scripts access to TypeSafe Jev, which returns typed yes/no, choice, and score judgments with calibrated probabilities, offline by default.

Trended earlier

PerryLink/jevcore on GitHub

Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk.

What do you want to do?

4 use cases

  • Route support tickets with typed Jev answers

    Ask Jev yes/no and choice questions about a ticket and act only on confident answers.

    View prompt
    In the PerryLink/jevcore repo, write a Node script that asks Jev a noul question ('Does this convey urgency?') and a choice question over the ticket text in <ticket file>. Expected output: the probability and confidence for each answer. Verify that the startup line reports egress=OFF and provider=mock, so no network call was made.

  • Install the jev plugin into DeepSeek Harness from a checkout

    Add the jevcore-dsh package and its core dependency to a DSH profile and confirm it is active.

    View prompt
    Using the PerryLink/jevcore checkout at <absolute path>, add packages/dsh and packages/core to the DeepSeek Harness profile with the dsh plugin command. Expected output: the jev plugin listed as active. Verify that the log contains provider=mock and egress=OFF before reporting success.

  • Serve the three Jev tools to a non-DSH MCP host

    Run the jevcore-mcp stdio server so any MCP host can call the jev_ask, jev_rank, and related tools.

    View prompt
    In the PerryLink/jevcore repo, start the jevcore-mcp stdio server with npx -y jevcore-mcp and register it with <MCP host config file>. Expected output: the host lists the three Jev tools. Verify that the egress report appears on stderr and that nothing else prints to stdout before the host connects.

  • Route Jev calls through an OpenRouter key

    Point the jevcore-dsh plugin at OpenRouter when a TypeSafe key is impractical.

    View prompt
    In the PerryLink/jevcore repo, configure the jevcore-dsh plugin with provider openrouter, openRouterApiKeyRef OPENROUTER_API_KEY, and model jev-latest. Expected output: a startup report naming the openrouter.ai endpoint. Verify that the report lists which state fields are sent before any live call is made.

How to use Jevcore

  1. Check you have what it needs: Node 20 or later for jevcore and jevcore-mcp, or Node ^22.19.0 or >=24.0.0 for jevcore-dsh; A local checkout of the repo for the DeepSeek Harness install path; DeepSeek Harness, if you use the plugin or the gates.
  2. Open PerryLink/jevcore on GitHub and read the README and license.
  3. Run npm install jevcore in the service so the core package is available to plain Node. (inferred, check the README)
  4. Check that the runtime is Node 20 or later, the requirement for the core package.
  5. Import the core package and call its ask function with a state object and noul and choice questions; the README shows this call through ctx.get('jev') inside DSH, so confirm the plain Node exports before wiring it. (inferred, check the README)
  6. Read result.answers for probability and confidence, and apply an explicit confidence floor as in src/policy.ts, sending unsure answers to a human queue.

These steps come from our top use case, Route support tickets with typed Jev answers, which also has a copy-paste agent prompt.

Jevcore alternatives · Best AI repos for Software and DevOps

About this repo

  • Who it is forDevelopers who run DeepSeek Harness, an MCP host, or a Node service and need routing or gating decisions without a chat model round-trip.
  • Why it is hot
  • LanguageTypeScript
  • Sourcegithub.com/PerryLink/jevcore · Back to Hot repos

Requirements

  • Node 20 or later for jevcore and jevcore-mcp, or Node ^22.19.0 or >=24.0.0 for jevcore-dsh
  • A local checkout of the repo for the DeepSeek Harness install path
  • DeepSeek Harness, if you use the plugin or the gates
  • A TypeSafe or OpenRouter key only if you choose a live route; the default is the offline mock
Maintain Jevcore? Add the Featured on Deduped badge

Paste this into your README:

[![Featured on Deduped](https://dedupedai.com/badge/perrylink-jevcore.svg)](https://dedupedai.com/use-cases/perrylink-jevcore/?ref=badge)

More badge styles and HTML

Questions about Jevcore

What is Jevcore?

jevcore is a TypeScript package that gives DeepSeek Harness, MCP hosts, and plain Node scripts access to TypeSafe Jev, which returns typed yes/no, choice, and score judgments with calibrated probabilities, offline by default. It is an open-source project on GitHub: https://github.com/PerryLink/jevcore.

Who is Jevcore for?

Developers who run DeepSeek Harness, an MCP host, or a Node service and need routing or gating decisions without a chat model round-trip.

What can I do with Jevcore?

4 use cases so far, for example: Route support tickets with typed Jev answers; Install the jev plugin into DeepSeek Harness from a checkout; Serve the three Jev tools to a non-DSH MCP host. Each has steps and a copy-paste agent prompt.

What do I need to run Jevcore?

Node 20 or later for jevcore and jevcore-mcp, or Node ^22.19.0 or >=24.0.0 for jevcore-dsh; A local checkout of the repo for the DeepSeek Harness install path; DeepSeek Harness, if you use the plugin or the gates; A TypeSafe or OpenRouter key only if you choose a live route; the default is the offline mock.

What are alternatives to Jevcore?

Other hot AI repos in Software and DevOps: Harness2, iFixAi, Orca, Diagram Design, AI Memory.

Is Jevcore safe to run?

Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.