[TimMikeladze]

Adds jevlang (jevlang.sh), a policy engine that declares routes, gates and actions in TypeScript or Python and answers each decision with Jev.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

Summary by CodeRabbit

• New Features
  • Added Jevlang to the project catalog, making its information available alongside other listed projects. The entry includes links to its repository and website, a description, and SDK and TypeScript classifications. It displays zero stars and an added date of October 13, 2026. Visitors can use the listing to identify the project and navigate to its external resources.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: e850d68d-a2c4-4136-aee0-c6b8f4ec14e7

📥 Commits

Reviewing files that changed from the base of the PR and between 99ef772 and 6a0dfb0.

📒 Files selected for processing: 1

• data/projects.json

Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review.

📝 Walkthrough

The project catalog adds jevlang with its repository, website, policy-engine description, SDK category, TypeScript language, zero stars, and October 13, 2026 added date.

Changes: Project catalog

Layer / File(s)	Summary
Add jevlang project entry data/projects.json	Adds jevlang and its repository, website, description, category, language, star count, and added date.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Feature

Suggested reviewers: scald

Merge Risk: ⚪ Minimal · up to 6a0df

The jevlang entry uses a registered category and is ready to merge after normal checks.

Pre-merge checks: 4 · 1

Failed checks: 1 warning

Check name	Status	Explanation	Resolution
Description check		The description identifies the project and explains where Jev fits. It does not include the required template sections or confirm that validation was run, generated files were not committed, and the a…	Use the repository template. Add the Project and Where Jev fits sections, then confirm npm run validate, confirm that README.md and site/index.html were not committed, and state that you are the author or link the project announcement…

Passed checks: 4 passed

Check name	Status	Explanation
Title check		The title, “Add jevlang,” clearly and concisely describes the main change.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Description check

Explanation

The description identifies the project and explains where Jev fits. It does not include the required template sections or confirm that validation was run, generated files were not committed, and the author or announcement source is linked.

Resolution

Use the repository template. Add the Project and Where Jev fits sections, then confirm npm run validate, confirm that README.md and site/index.html were not committed, and state that you are the author or link the project announcement.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Warning

⚠️ This pull request has been flagged as potential spam (promotional) by CodeRabbit slop detection and should be reviewed carefully.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[scald]

Landed on main as bb9da3c with you as the commit author, live on https://awesomejev.com after the deploy finishes. Closing rather than merging because every PR appends to the same data file and they conflict with each other; landing directly keeps your authorship. Thanks!