📘 Get all Warframe items directly from Warframe's API. No more messy wikia scraping.
C-Rank Grade: B (Solid) - 62/100
External PR Merge Rate: 67%
Response Time: 2h
First Timer Success: 67%
WFCD/warframe-items has a recorded first-timer success rate of 66.7%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in WFCD/warframe-items respond to incoming external pull requests in approximately 2.0 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 61.9 places WFCD/warframe-items in the B tier.
The external contributor pull request merge rate for WFCD/warframe-items is 66.7%, based on public PR activity from non-core contributors.
WFCD/warframe-items currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
📘 Get all Warframe items directly from Warframe's API. No more messy wikia scraping.
Active maintainer team in WFCD/warframe-items welcoming community pull requests and bug fixes.
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/WFCD/warframe-items?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 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (83% approval). Large PRs (>500 lines) take ~10 hours (30% approval). Keep your diff compact for rapid review.
Describe the bug In the provided /data/jsons/ on the github a few items are missing thier wikiaUrls NodeJS Version NA npm Version NA @wfcd/items Version v1.1275.35 Access Method github download What happened? Three items from the data/json do not have the "wikiaUrl" field but they do have entries on the wiki: - Warframes.json Bonewidow Voidrig - Melee.json Dark Split-Sword not sure whats causing it, but I found this because I was trying to get the wiki url for all the masterable items and my thing was breaking because these ones were missing. not really a big deal as i can just add in exceptions for these but still an issue nonetheless.
Describe the bug In Hotfix 43.0.2, Neo V11 was vaulted and Neo V12 was newly added. Relics.json currently lists the old relic as unvaulted and the new relic as vaulted. NodeJS Version n/a npm Version n/a @wfcd/items Version n/a Access Method github download What happened? In Hotfix 43.0.2, Neo V11 was vaulted and Neo V12 was newly added. /data/json/Relics.json currently incorrectly lists the old relic as unvaulted and the new relic as vaulted. The official drop tables seem to be correct, with the new Neo V12 having listed drop locations and the old Neo V11 having none. See also the 43.0.2 patch notes: https://www.warframe.com/en/patch-notes/pc/43-0-2
Describe the bug These are known missing data aspects that we can't retrieve or update NodeJS Version N/A npm Version N/A @wfcd/items Version N/A Access Method npm Package (Default) What happened? Missing data issues: #815 #557 Clashing Forest (stance mod)
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 WFCD/warframe-items, 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 WFCD/warframe-items acknowledge new external contributions in approximately 2 hours. 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.
WFCD/warframe-items has a recorded first-timer success rate of 66.7%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 hours. 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 61.9 places WFCD/warframe-items in the Solid 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, WFCD/warframe-items 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 WFCD/warframe-items 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.