
not indicated, and the general idea of dataviz is to communicate clearly. when you have a number, what it represents should be noted, and the units. if I see a number in that context, I assume it's calling out the value displayed.
the x axis is also a bit off, would ideally plot the date of the release and use a proper time axis.
a title is also good to have, maybe a data table.
sorry to be cranky but those who are downvoting , try to be clear, learn some standards, or stay away from publishing charts. you can even ask AI to clean up your code to conform to a standard. Soft skills are important for an engineer. You need to explain the work in clear, persuasive language and dataviz. or you can be, I'm a super-smart engineer, you figure out what I'm trying to say, I don't need to worry about making your eyes bleed. crikey.
https://www.datavizstyleguide.com/
https://www.amazon.com/Better-Data-Visualizations-Scholars-R...
Better Data Visualizations by Jonathan Schwabish is the best. He combines all the insight from recent data biz books like Storytelling with Data or Cairos series into a comprehensive guide. Even has a practical section on visualizing qualitative data, which I never see.