Skip to content

Add schema-envoy to tools - #58

Merged
jviotti merged 1 commit into
sourcemeta:masterfrom
tamerkalla:add-schema-envoy
Aug 29, 2026
Merged

jviotti merged 1 commit into
sourcemeta:masterfrom
tamerkalla:add-schema-envoy

Conversation

@tamerkalla

@tamerkalla tamerkalla commented Aug 28, 2026 •

Copy link
Copy Markdown
Contributor

Adds schema-envoy under tools.

Every LLM provider accepts a subset of JSON Schema, so client libraries delete the keywords the provider does not list. That deletion widens the accepted value set (the converted schema accepts instances the source schema rejects), and it is normally not reported. schema-envoy performs the conversion, reports every keyword it removed, and compiles a residual validator over precisely those dropped constraints, so a caller can reject a widened value rather than only learn that widening occurred.

It is distinct from Schema Gateway, already listed: that entry compiles a schema into provider-ready request payloads and lints portability. schema-envoy's output is the report and the residual validator over what conversion cost, rather than the request payload.

Zero-config for the built-in provider targets, dual ESM/CJS, published with npm provenance.

I have added the entry to data.yaml and regenerated README.md with npm install && npm start, as CONTRIBUTING.md asks.

@cla-assistant

cla-assistant Bot commented Aug 28, 2026 •

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@tamerkalla

Copy link
Copy Markdown
Contributor Author

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Signed

@jviotti

jviotti commented Aug 29, 2026

Copy link
Copy Markdown
Member

Awesome!

@jviotti
jviotti merged commit 284842b into sourcemeta:master Aug 29, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants