it works!
ahoy @maelle @hrbrmstr @jonocarroll

Basic functionality works - please open issues with any thoughts, desires, suggestions. I'll open a couple already too. And most importantly: Please take what I've done, improve, polish, extend, help out! Thanks in advance
And @maelle you're the poster child for the image coz you have the most bestest matches for "some good stuff" - I think you can take that as a personal compliment, so congratulations!
Very cool and :joy:
Recently I was looking for a repo and it took me more than expected to find it because it lacked a repo description. I remembered someone starring it but that wasn't enough since the name itself wasn't self-explanatory... not linked to your tool but once should really promote having good repo descriptions 😀
The only extra info that is directly available via GH API v4 that is likely useful here would be labels, but it would of course also be easy to trawl all README.md files and do a text analysis of those. That would take enormously longer but might be worth considering with some nifty caching.
you mean the repo topics?
I like structured info like repo topics better.
And see this other place where keywords can live https://github.com/ropensci/codemetar/blob/master/DESCRIPTION#L76 (you can add any schema term to DESCRIPTION with the "X-schema.org-" prefix, and it's digested by codemetar::write_codemeta to codemeta.json
oh no, whoops, the labels i flagged are actually just the issue labels. What i meant was of course and indeed repositoryTopics.