awesomejev

Community project / Agent and developer tooling

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.

Open the original resource ↗ See it in the full directory Browse all Agent and developer tooling
Awesome Jev share card for perch 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

  • 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 →

  • pi-jev

    Pi extension with a shadow-mode tool-call gate, output judge, and a general typed jev_ask tool.

    Read listing →

  • pi-jev-compaction

    Pi extension that asks Jev which older tool results to hide after context pressure rises, retains the original session messages, and exposes a jev_read tool to recover an output without rerunning its command; it protects recent results and leaves context unchanged on API failure, but Jev sees bounded conversation and tool-output excerpts that may contain private data, and tests do not establish live relevance quality or cost savings.

    Read listing →