awesomejev

Community project / Agent and developer tooling

oxlint-plugin-jev

Experimental Oxlint plugin that asks Jev Noul questions about functions, calls, JSX elements, or files and reports matches above a chosen cutoff. It sends matched snippets to TypeSafe; API failures skip checks by default, so set ci: "fail" in CI. Keep it out of editor linting because edits can trigger paid calls.

Open the original resource ↗ See it in the full directory Browse all Agent and developer tooling
Awesome Jev share card for oxlint-plugin-jev Download share card

Share this listing

Maintaining this project? Share its link, badge, or image. Listed means included, not endorsed.

Download share card

This is an independent community listing. Check the source, license, data handling, and evaluation caveats before relying on a project. Inclusion is not an endorsement or security review.

Found an outdated or inaccurate detail? Report a correction →

Explore more in Agent and developer tooling

  • patdown

    CLI, GitHub Action, and agent hooks that judge files or changes against Markdown rules with a provider-swappable Jev backend and configurable probability threshold; it sends matched file content to TypeSafe, has no request budget or result cache yet, and its semantic verdicts need human review for consequential gates.

    Read listing →

  • perch

    Code scanner that parses methods and their call graph, asks Jev typed questions about each method in scope, and ranks potential defects and security findings; --since scopes CI runs. It sends method source to TypeSafe and reads every method in scope, so review request cost and findings before using it as a gate.

    Read listing →

  • pi-heed

    Pi extension that turns constraints stated in conversation (English and Chinese) into a scoped, replayable policy (deny, allow, exceptions, once/run permissions, ask-first, tests-before-push) and checks side-effecting tool calls against it before they run; rules handle side effects and paths while Jev only classifies how each message changes the policy, re-checks exceptions and skips tools a free-text rule cannot concern; ships a replayable benchmark and an experiment log on Jev calibration and question design; experimental, shadow mode by default, fails open, and the benchmark is scripted rather than drawn from real sessions.

    Read listing →