inventree/InvenTree - Open Source PR Review Scorecard

Open Source Inventory Management System

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

External PR Merge Rate: 88%

Response Time: 2d

First Timer Success: 65%

Frequently Asked Questions

Is inventree/InvenTree welcoming to first-time open-source contributors?

inventree/InvenTree has a recorded first-timer success rate of 64.7%. 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 inventree/InvenTree respond to incoming external pull requests in approximately 39.8 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 64.9 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 64.9 places inventree/InvenTree in the A tier.

What is the external contributor pull request merge rate for inventree/InvenTree?

The external contributor pull request merge rate for inventree/InvenTree is 87.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in inventree/InvenTree?

inventree/InvenTree currently has 10 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

inventree
inventree/InvenTreeA•Welcoming7.4k
GitHub
Back to Explorer
inventree

inventree/InvenTree

7,437
A•Welcoming(65/100)Python

Open Source Inventory Management System

Compare•
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Quality Architect

Warmth Score
6.8/10
Patience Score
7.3/10
Nitpick Rate
41%

Established Python ecosystem in inventree/InvenTree. Maintains structured code review standards for external contributors.

Top PR Submission Do's

  • •Ensure code complies with Python style conventions
  • •Keep PRs scoped and well-documented
  • •Include relevant test coverage for changes

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
  • •Do not mix unrelated refactors with feature work
Response Velocity
1 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
87.7%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
26 core
Highly collaborative maintainer core
Diagnostic Health HUD
87.7%
Merge Gauge
64.7%
1st-Timer
Community Vibe55/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

Please verify that this feature request has NOT been suggested before. I checked and didn't find a similar feature request Problem statement All table headers shows the title as horizontal text. A column like Temperature coefficient [±ppm/°C] will take a lot of width, while the data could be something small like 100. This is how it looks now: Suggested solution By adding an option to rotate the text in the table header 90° we can get a really compact table that wastes less screen space. This is how it could look: Alternatively, have the buttons at the bottom. Describe alternatives you've considered I have a working proof-of-concept CSS that seems to work in Gecko and WebKit based browsers. There are still a few things to figure out. A better way to include the CSS. I have not touched any React code yet. I just included some raw CSS Margins could probably be adjusted slightly to make it even more compact. Some contents of the table, like the bool, does need some CSS adjustment

📅 Opened Aug 7, 2026💬 3 comments
Quality: 80/100Contribute

Please verify that this bug has NOT been raised before. I checked and didn't find a similar issue Describe the bug* The docs on stock ownership say that if stock ownership is enabled when you edit a location you can set the default owner of a location for stock in the UI. However, the actual stock location edit UI is different from the one in the docs and is missing the "Owner" field. My memory said this used to work at some point. This may be a regression, or I might be missing a new setting to enable this. Steps to Reproduce Login as admin to demo instance go to "system settings" -> "Stock" Enable "Stock Ownership Control" Go to a stock location and open the edit panel Note lack of "ownership" field Expected behaviour Stock locations should present the "ownership" field in the edit window when stock ownership is enabled. Deployment Method Docker Version Information InvenTree-Version: 1.3.5 Django Version: 5.2.15 Commit Hash: d8cac9b Commit Date: 2026-06-11 Commit Branch: null

📅 Opened Aug 1, 2026💬 2 comments
Quality: 65/100Contribute

Please verify that this feature request has NOT been suggested before. I checked and didn't find a similar feature request Problem statement Its quite hard to see the minimum and maximum stock allowed directly in the parts table unless its set. Suggested solution if you guys can add an option to view minimum & maximum stock in the select column of the parts and a option to bulk change the minimum & maximum stock it will be easy to update and view Describe alternatives you've considered Manually updating the stock Examples of other systems No response Do you want to develop this? I want to develop this.

📅 Opened Jul 15, 2026💬 2 comments
Quality: 65/100Contribute

Please verify that this feature request has NOT been suggested before. I checked and didn't find a similar feature request Problem statement Hi, when we want to change information in multiple object (for example 30 parts) , we have to filter list, click on the first object, change the value, return to the list , open the second object, change the value ... Suggested solution I think it's a good idea to add two icons on banner "Previous" and "Next" for simplify navigation between the filter list objects When object change, the focus field must be the same. Best regards Describe alternatives you've considered Allow field edition as parametrics values Examples of other systems For example Maximo Ibm do this Do you want to develop this? I want to develop this.

📅 Opened Jul 14, 2026💬 21 comments
Quality: 90/100Contribute

Please verify that this feature request has NOT been suggested before. I checked and didn't find a similar feature request Problem statement the current spotlight only supports very simple actions like creating objects / taking actions. search is also seperate. Suggested solution use something like https://github.com/dip/cmdk that allows more powerful and faster navigation through actions / links to enable pure keyboard-based usage of the interface. Describe alternatives you've considered extending current actions / integrating at least search into current spotlight Examples of other systems vercel has pretty powerfull nav Do you want to develop this? I want to develop this.

📅 Opened Apr 22, 2026💬 6 comments
Quality: 70/100Contribute
Looking for more Python beginner tasks?Explore Python 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 inventree/InvenTree

When evaluating whether to contribute to inventree/InvenTree, 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 inventree/InvenTree acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 87.7% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to inventree/InvenTree

01

Is inventree/InvenTree welcoming to first-time open-source contributors?

inventree/InvenTree has a recorded first-timer success rate of 64.7%. 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 ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 64.9 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 64.9 places inventree/InvenTree in the Welcoming tier.

04

What is the external contributor pull request merge rate for inventree/InvenTree?

The external pull request merge rate is 87.7%. 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 inventree/InvenTree?

Yes, inventree/InvenTree currently has 10 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rankâ„¢ Indexing Standard

All metrics displayed for inventree/InvenTree 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.

inventree/InvenTree • 64.9/100 C-Rank (A-Tier) | GetMerged