Chrome extension to add a metadata layout on top of the standard Salesforce UI to improve the productivity and joy of Salesforce configuration, development, and integration.
C-Rank Grade: B (Solid) - 55/100
External PR Merge Rate: 29%
Response Time: 17h
First Timer Success: 25%
tprouvot/Salesforce-Inspector-reloaded has a recorded first-timer success rate of 25.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in tprouvot/Salesforce-Inspector-reloaded respond to incoming external pull requests in approximately 17.4 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 54.7 places tprouvot/Salesforce-Inspector-reloaded in the B tier.
The external contributor pull request merge rate for tprouvot/Salesforce-Inspector-reloaded is 28.6%, based on public PR activity from non-core contributors.
tprouvot/Salesforce-Inspector-reloaded currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Chrome extension to add a metadata layout on top of the standard Salesforce UI to improve the productivity and joy of Salesforce configuration, development, and integration.
Growing JavaScript project in tprouvot/Salesforce-Inspector-reloaded 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/tprouvot/Salesforce-Inspector-reloaded?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~11 hours (36% approval). Large PRs (>500 lines) take ~83 hours (15% approval). Keep your diff compact for rapid review.
Prerequisites I've read the common issues and the one I'm about to create is not one of those documented. I've searched in the existing issues and the one I'm about to create is not one of those created. I've read the release note and the one I'm about to create is not already fixed. Describe the bug Fields with the "location" type display "Error" in the Show All Data -> Get field usage button. In this case, the displayed value should be the same as that of the related latitude or longitude field. To Reproduce Find a object that has the "location" type field in Show All Data Click "Get field usage" Check the output The example in image was based on Service Appointment SObject, from Field Service package. Version 2.0 What browser are you using? Chrome
Description Keyboard shortcuts added in #171 work on Chrome but are not available on Firefox. On Firefox, about:addons > Manage Extension Shortcuts lists Salesforce Inspector Reloaded under "The following extensions do not have shortcuts", so users cannot assign any shortcut (Firefox only allows assigning shortcuts to commands declared by the extension). Cause addon/manifest.json (Chrome build) declares a commands block with all the shortcut commands. addon/manifest-firefox.json does not declare any commands key, so no command is exposed to Firefox. The chrome.commands.onCommand listener in addon/background.js is shared by both builds. Note that the fallback branch opens extension pages with a hardcoded chrome-extension:// URL, which would not work on Firefox (moz-extension:// scheme); chrome.runtime.getURL() would work for both browsers. Environment Firefox on macOS Salesforce Inspector Reloaded 2.0.0
Prerequisites I've read the common issues and the one I'm about to create is not one of those documented. I've searched in the existing issues and the one I'm about to create is not one of those created. I've read the release note and the one I'm about to create is not already fixed. Describe the bug In dependencies results view link for Validation rules is not correct so it doesn't redirect to particular validation rule. Example: Link behind Open in Salesforce is: .../lightning/setup/ObjectManager/03d4w000001tfy2AAA/ValidationRules/view while the correct link would be: .../lightning/setup/ObjectManager/ValidationRules/03d4w000001tfy2AAA/view To Reproduce Find dependencies for any fields that are used in validation rules and click the Open in Salesforce link to see if the redirect is working or not. P.S. Version used is 2.0 but Version picklist on the ticket can go only up to 1.27 :) Version 1.27 What browser are you using? Microsoft Edge
Prerequisites I've read the common issues and the one I'm about to create is not one of those documented. I've searched in the existing issues and the one I'm about to create is not one of those created. I've read the release note and the one I'm about to create is not already fixed. Describe the bug I configured the "Generate SOQL queries with Agentforce" prompt template and enabled it when v1.27 was first released and it was working fine. However, I attempted to use it again today in a demo and realized that it's including syntax tags. Maybe something changed in the agentforce engine that requires an updated prompt? UPDATE It appears this is happening to me about 50% of the time, I can run the same prompt multiple times and get good outputs on some and bad outputs that include the syntax tags on others To Reproduce Configure the prompt template and browser extension options as described in the Features documentation Go to Data Export, click the Agentforce/Einstein icon in the
Prerequisites I've read the common issues and the one I'm about to create is not one of those documented. I've searched in the existing issues and the one I'm about to create is not one of those created. I've read the release note and the one I'm about to create is not already fixed. Describe the bug When creating a field using field creator and assigning to a profile that cannot access that object, it will show an error, despite the field actually being created. To Reproduce Open field creator and select an object such as Account Add a field label and under permissions assign the chatter free user profile with edit access Deploy the field and note the error message, indicating to the user that it failed to create. Search for the field and you will see it was created anyway on the account object. Version beta What browser are you using? Chrome
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 tprouvot/Salesforce-Inspector-reloaded, 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 tprouvot/Salesforce-Inspector-reloaded acknowledge new external contributions in approximately 17 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 28.6% were successfully merged into the primary branch.
tprouvot/Salesforce-Inspector-reloaded has a recorded first-timer success rate of 25.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~17 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 54.7 places tprouvot/Salesforce-Inspector-reloaded in the Solid tier.
The external pull request merge rate is 28.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, tprouvot/Salesforce-Inspector-reloaded currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for tprouvot/Salesforce-Inspector-reloaded 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.