jsonrainbow/json-schema - Open Source PR Review Scorecard

JSON Schema for PHP

C-Rank Grade: A (Welcoming) - 61/100

External PR Merge Rate: 65%

Response Time: 7h

First Timer Success: 100%

Frequently Asked Questions

Is jsonrainbow/json-schema welcoming to first-time open-source contributors?

jsonrainbow/json-schema has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in jsonrainbow/json-schema respond to incoming external pull requests in approximately 7.3 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 61.4 C-Rank™ score (A Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 61.4 places jsonrainbow/json-schema in the A tier.

What is the external contributor pull request merge rate for jsonrainbow/json-schema?

The external contributor pull request merge rate for jsonrainbow/json-schema is 65.4%, based on public PR activity from non-core contributors.

Are there Good First Issues available in jsonrainbow/json-schema?

jsonrainbow/json-schema does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

jsonrainbow
jsonrainbow/json-schemaA•Welcoming3.6k
GitHub
Back to Explorer
jsonrainbow

jsonrainbow/json-schema

3,626
InactiveA•Welcoming(61/100)PHP

JSON Schema for PHP

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

High-Friction Gatekeeper

Warmth Score
5.0/10
Patience Score
6.0/10
Nitpick Rate
65%

Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in jsonrainbow/json-schema.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Use conventional commit messages and clean branch names
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
7 hours
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
65.4%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
100.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
8 core
Highly collaborative maintainer core
Diagnostic Health HUD
65.4%
Merge Gauge
100.0%
1st-Timer
Community Vibe81/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for jsonrainbow/json-schema
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/jsonrainbow/json-schema)](https://getmerged.abhishekco.de/jsonrainbow/json-schema?utm_source=github&utm_medium=badge)

Active Good First Issues (4)

View on GitHub

If you try to run the following code with your package (version 6.10.0) : $validator = new Validator(); $payload = json_decode(json_encode(["test" => "1"])); $validator->validate( value : $payload, schema : json_decode(json_encode([ "type" => "object", "properties" => [ "test" => [ "type" => "boolean", ] ], "required" => ["test"], "additionalProperties" => false, '$schema' => 'file://' . PROJECT_ROOT . '/vendor/justinrainbow/json-schema/dist/schema/json-schema-draft-04.json' ])), checkMode: Constraint::CHECK_MODE_VALIDATE_SCHEMA | Constraint::CHECK_MODE_APPLY_DEFAULTS | Constraint::CHECK_MODE_COERCE_TYPES ); if (!$validator->isValid()) { $validation_errors = []; foreach ($validator->getErrors() as $error) {

📅 Opened Sep 14, 2026💬 3 comments
Quality: 90/100Contribute

Validating a string containing a NUL byte against {"type": "string", "format": "date"} throws instead of reporting the instance invalid. <?php require 'vendor/autoload.php'; $validator = new JsonSchema\Validator(); $data = "2020-01-01\x00"; $validator->validate($data, (object)['type' => 'string', 'format' => 'date']); var_dump($validator->isValid()); Expected: bool(false) - the value is not a valid RFC 3339 full-date. Actual: PHP Fatal error: Uncaught ValueError: DateTime::createFromFormat(): Argument #2 ($datetime) must not contain any null bytes in .../src/JsonSchema/Constraints/FormatConstraint.php:157 Versions: json-schema 6.10.0 and 6.7.2.0, PHP 8.1.34. Both affected. Cause FormatConstraint::validateDateTime() (src/JsonSchema/Constraints/FormatConstraint.php:157) calls: $dt = \DateTime::createFromFormat($format, (string) $datetime); In PHP 8, DateTime::createFromFormat() raises ValueError when the datetime argument contains a NUL byte, rather than returning false as it did in

📅 Opened Aug 18, 2026💬 2 comments
Quality: 90/100Contribute

There are more PHP files which we should check for styling issues: bin/run-test-case bin/validate-json demo/demo.php

📅 Opened Aug 14, 2026💬 0 comments
Quality: 75/100Contribute

I have found that if a payload contains a date-time with more than 6 fractional seconds it will fail validation. Issue seems to stem from the fact that PHP DateTime will only allow 6 digits and fail after that. Could it truncate the fractional seconds to 6 digits before parsing it? Rfc3339::createFromString('2026-07-23T10:46:08.4070000Z')); var_dump(DateTimeImmutable::createFromFormat('Y-m-d H:i:s.uP', '2026-07-23 10:46:08.4070000' . 'Z', new \DateTimeZone('UTC'))); var_dump(DateTimeImmutable::createFromFormat('Y-m-d H:i:s.uP', '2026-07-23 10:46:08.407000' . 'Z', new \DateTimeZone('UTC')));

📅 Opened Jul 28, 2026💬 3 comments
Quality: 90/100Contribute
Looking for more PHP beginner tasks?Explore PHP GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for jsonrainbow/json-schema

When evaluating whether to contribute to jsonrainbow/json-schema, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of jsonrainbow/json-schema acknowledge new external contributions in approximately 7 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 65.4% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to jsonrainbow/json-schema

01

Is jsonrainbow/json-schema welcoming to first-time open-source contributors?

jsonrainbow/json-schema has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~7 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 61.4 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 61.4 places jsonrainbow/json-schema in the Welcoming tier.

04

What is the external contributor pull request merge rate for jsonrainbow/json-schema?

The external pull request merge rate is 65.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in jsonrainbow/json-schema?

jsonrainbow/json-schema does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for jsonrainbow/json-schema are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.