A typeface that protects written content by poisoning unauthorized AI training datasets.
C-Rank Grade: A (Welcoming) - 56/100
External PR Merge Rate: 67%
Response Time: <1h
First Timer Success: 100%
isaqueseneda/shieldfont 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.
Maintainers in isaqueseneda/shieldfont respond to incoming external pull requests in approximately 0.7 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
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 56.0 places isaqueseneda/shieldfont in the A tier.
The external contributor pull request merge rate for isaqueseneda/shieldfont is 66.7%, based on public PR activity from non-core contributors.
isaqueseneda/shieldfont currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A typeface that protects written content by poisoning unauthorized AI training datasets.
Strict review standards in isaqueseneda/shieldfont. Ensure PR scope matches issue requirements closely before requesting review.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/isaqueseneda/shieldfont?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (83% approval). Large PRs (>500 lines) take ~3 hours (30% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in TypeScript.
No repository description available.
Monorepo for tools developed by the Rush Stack community
Tool to generate circles for block building games like Minecraft
Two things about what we can honestly say on screen reader support. We need someone to test with JAWS We test with real NVDA on a Windows runner every commit, and by hand with VoiceOver on macOS. JAWS is the other big share of Windows screen reader use and we haven't run it, so "verified on NVDA" covers less than it sounds like. The docs say JAWS is untested everywhere they mention it. What would help is someone with a JAWS licence walking a shielded page and telling us what they hear: Does it ever read the decoy text out loud? It shouldn't, that's the whole point. Can you find the Uncover button, and does its name make sense? After you press it, does it read the text out, or do you have to go find it? See #7, NVDA doesn't read it out and VoiceOver does. No formal audit needed. "I pressed the thing and here's what it said" is genuinely useful and better than us guessing. The NVDA job should be able to fail the build .github/workflows/test.yml runs the NVDA job with continue-on-error:
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to isaqueseneda/shieldfont, 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 isaqueseneda/shieldfont acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.7% were successfully merged into the primary branch.
isaqueseneda/shieldfont 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.
The initial maintainer response time averages ~<1 hour. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
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 56.0 places isaqueseneda/shieldfont in the Welcoming tier.
The external pull request merge rate is 66.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, isaqueseneda/shieldfont currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for isaqueseneda/shieldfont 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.