chris48s
commented
1 year ago One of the things that makes this challenging is we can easily parse data in popular serialization formats like JSON, XML and Yaml.
Go.mod is a custom format (I guess it is a module of go code? Its not an ecosystem I'm familiar with) so we'd have to be able to parse that format in javascript in order to extract the data from it.
Its not an impossible problem, but it does put it in a category of badge that is more difficult to implement in shields.io because it requires finding or implementing a custom parser.
📋 Description
As a project template maintainer, I want to present my dependency versions on my GitHub Readme. So people know if I'm using the latest and greatest version of that one truly awesome framework they wanna work with, or if the repo is just dead and unmaintained.
Also, for my use case it must be possible to specify a subfolder in the monorepo
🔗 Data
There is already a badge to display the go version. Like npm everything is documented inside the go.mod file which must be parsed and then everything can be read
🎤 Motivation
As mentioned, you could use it to display it on your main page to see if dependencies have an older version of a framework and needs to be updated. It can warn users from using way too old versions of frameworks