
We enable the reliable use of JSON data format.
Showing 5 of 19 projects. Click any project card for scope, mentors, and proposal studio.
Mentors: Student: Rodiat Hammed
The JSON Schema validation test suite currently maintains a separate folder for each released version of the specification. This means most tests exist as identical copies across multiple folders, and every new test or bug fix must be applied in several places. This does not scale. The annotation test suite already solves this problem using a `compatibility` field that indicates which versions each test applies to, allowing test runners to filter accordingly. This project brings that same approach to the validation test suite, collapsing all per-version folders into a single unified suite with no duplicate tests.
Mentors: Student: srivastava-diya
vscode-json-languageservice, the library powering JSON editing in VSCode currently supports only JSON Schema draft-07. The architectural coupling between its validator and editor features means draft support cannot be extended by simply swapping the validator. This project aims at building a drop-in replacement that matches the exact API surface of vscode-json-languageservice while replacing the validator with @hyperjump/json-schema, bringing full support for draft-04 through draft-2020-12. By the end of GSoC, all 13 features of the existing library will be implemented and tested, backed by a MatchingSchemaCollector EvaluationPlugin as the core data layer, a working VSCode extension, and a test suite verifying drop-in compatibility with the existing implementation.
Mentors: Student: Tushar_Verma
JSON Schema defines 18 format types (uri, email, date-time, ipv4, etc.) but the official test suite has minimal coverage for most of them. Without shared test cases derived from the actual RFC grammars, implementations diverge silently - ajv-formats accepts space-separated date-times, python-jsonschema reduces email validation to checking for "@", and no one can tell which behavior is correct. This project builds a comprehensive, RFC-grounded test suite for all 18 formats. Every test case is derived directly from the ABNF production rules in the governing RFC, verified against at least two implementations, and documented with a direct RFC citation. Pre-proposal research across 10 formats has already produced 11 filed issues across ajv-formats, sourcemeta/core, libidn2, and golang/go. Deliverables: 200-280 test cases structured as PRs to the JSON Schema Test Suite repository, covering all 18 formats in JSON Schema 2020-12, with Bowtie integration as a stretch goal.
Mentors: Student: Vidit_Agarwal
Bowtie is a meta-validator for the JSON Schema specification, giving users a way to execute and compare how different implementations behave against the official test suite. Currently, Bowtie only supports validating instances on a simple pass/fail basis, comparing implementations solely on their correctness regarding strict schema validation. However, the JSON Schema specification also defines "Annotations"—rich metadata attached to schemas like descriptions, deprecation notices, and default values. This project primarily focuses on integrating the official Annotation Test Suite into Bowtie's architecture. This involves upgrading Bowtie's core protocol and updating numerous language-specific test harnesses to successfully extract and transmit this annotation data natively. By building a dedicated interactive dashboard within the Bowtie website, this project will allow users to easily visualize annotation compliance across languages. Ultimately, this gives users another crucial dimension to evaluate different implementations, ensuring the ecosystem correctly surfaces important specification metadata alongside standard validation results.
Mentors: Student: Sumit goyal
JSON Schema Studio visualizes JSON Schemas as interactive graphs, helping developers understand complex structures. While the current version works well, there are areas where rendering correctness and user experience can be improved. This project focuses on ensuring correct dependency-based rendering (especially for $defs), improving graph navigation, and enhancing synchronization between the editor and visualization. It will also address issues like edge collisions and unstable rendering during live edits. Additionally, features like validation error navigation, file upload, and visualization export will be introduced to improve usability. The final deliverables include: - Dependency-aware rendering using topological sorting - Improved graph interaction and navigation - Validation error navigation in the editor - Reduced edge collisions - Stable rendering during live edits - File upload and export support These improvements will make the tool more accurate, interactive, and useful for developers.