feat: expose research and remediation counts in top_security.json#236
Merged
Merged
Conversation
The top_security.json output now carries per-login `research` and `remediation` counts alongside the total `count`. The ranking still sorts by total (research + remediation together), so the front end can display both families in separate columns while keeping a single leaderboard. Remediation credits are a valuable signal on their own: the fixers of PrestaShop vulnerabilities push their commits through the private security repository, get their work republished by the core team, and therefore never appear as the author on any public PR — so this is the only structured source that surfaces them. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Progi1984
approved these changes
Jul 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Follow-up to #235. After discussion with the security team, the previous choice to keep only research credits in the leaderboard turned out to be wrong on its own terms: the assumption was that remediation credits go to core developers who are already surfaced in the PR/commit leaderboards, so keeping them would double-count. In practice the opposite holds — the developers who patch PrestaShop vulnerabilities push their commits through the private security repository, then have their work republished by the core team, so they never appear as the author on any public PR. The remediation credits on published advisories are therefore the only structured source that surfaces this work, and it's exactly the invisible contribution the security team wants recognised (Clotaire's point on the community thread: research reports are not the current bottleneck, the patching work is — 5× the effort of the initial report).
What this does
Small change on top of #235:
top_security.jsonnow carriesresearchandremediationcounts per contributor, alongside the existing totalcount.count— one unified leaderboard, no separate boards — so the front end can display research and remediation as breakdown columns.countdescending, then login alphabetically (unchanged).Output schema
{ "updatedAt": "2026-07-08", "items": [ { "rank": 1, "login": "matthieu-rolland", "name": "Matthieu Rolland", "avatar_url": "...", "html_url": "...", "count": 4, "research": 0, "remediation": 4 }, ... ] }Notes
phpstanandphp-cs-fixerpass.traces:fetch:security-advisories:gh_security_advisories.jsonalready stored all credit roles as raw data, only the generate step filters.🤖 Generated with Claude Code