The codemeta2cff I wrote in Go presumes having to pick one interpretation of an ambiguous spec.
I've since originally writing codemeta2cff in Go I've switch to generating CITATION.cff and about.md from codemeta.json via a Pandoc templates. It is a much more flexible process. Instead of installing codemeta2cff I'd recommend installing Pandoc. Then you can use the templates from https://github.com/caltechlibrary/codemeta-pandoc-examples generate many types of files from the codemeta.json contents.
This General approach would allow you to generate the following easily
The codemeta2cff I wrote in Go presumes having to pick one interpretation of an ambiguous spec.
I've since originally writing codemeta2cff in Go I've switch to generating CITATION.cff and about.md from codemeta.json via a Pandoc templates. It is a much more flexible process. Instead of installing codemeta2cff I'd recommend installing Pandoc. Then you can use the templates from https://github.com/caltechlibrary/codemeta-pandoc-examples generate many types of files from the codemeta.json contents.
This General approach would allow you to generate the following easily