I’m Maanvi, and I’m starting to contribute to the Plugin Modernizer Stats Visualization project for GSoC 2026. I’m planning my first PR and wanted to get some feedback.
The idea is to create a simple chart showing the number of plugins using deprecated APIs using the existing metadata from metadata-plugin-modernizer. My goal is to:
Read the JSON/CSV data
Build a React + TypeScript chart (probably with ECharts)
Keep it small, clear, and mobile-friendly
I think this will be a good first step before adding filters, dashboards, or plugin detail pages.
Would love to hear your thoughts—does this approach make sense? Any suggestions or tips before I start coding?
Hi Maanvi @extra_fair_10 thanks for your interest in the project! I am curious though have you confirmed with the lead mentor Valentin @jonesbusy about the setup before you proceed with a PR? (Like which repo(s) the project work will be carried out?)
Yes, React with Echarts would be an ideal choice for the charts as that is what the Jenkins Infra team is comfortable working with.
Hi @krisstern , thank you for the feedback! I’m glad to hear React and ECharts are the right path. I haven’t cofirmed the specific repository with @jonesbusy yet, so I will reach out to him now to make sure I’m working in the right place before I start the PR. I’ll update here once I have the green light!
Apologies for the private message, @krisstern and @jonesbusy ! I’m still learning the community communication norms and will keep everything here moving forward.
@jonesbusy , to follow up on the discussion, could you please clarify:
Target Repository: Which repository should I use to host the frontend code for this PR?
Data Source: Where can I find the official metadata-plugin-modernizer JSON/CSV file to use as my data source?
Hi @jonesbusy, just following up on my earlier message about the plugin-modernizer stats visualization setup. I’m ready to start coding once the repository and data source are clarified. Thanks!
Hi @jonesbusy,
Thank you for the guidance. I will go through the repositories listed on the project idea page and check the metadata sources there.
Thanks!
Hi all,
I’ve created a PR (#718) on the branch ‘deprecated-api-visualization’ for the Plugin Modernizer Stats Visualization (based on the example PRs in the repo). When you get a chance, I’d appreciate any feedback or suggestions on it.
Thanks!
Why we just didn’t implement a workflow/GH action that fetch this data regurlarly and transform in a format we need?
Is usage-by-plugins.json accurate? Could we have better results using OpenRewrite? What woulb be needed to include deprecated information on plugin metadata?
I’m closing the PR because this is not the correct approach
That makes sense — I see now that this repository is intended more for data processing rather than hosting a visualization.
I’ll look into implementing this as a GitHub Action that periodically fetches the plugin usage data and transforms it into a structured format that could potentially be added to plugin metadata.
Also interesting point about accuracy — I’ll explore whether tools like OpenRewrite could provide more reliable deprecated API detection.
