I think a feature like this could be tricky to add because not all projects published to npm are on GitHub. In addition, information about a package's repository URL provided by package.json could be incorrect or even misrepresented (as there is no mechanism that validates this is correct).

That's a very good point. Is there potential for some sort of rating system within ConstructHub (appstore like rating features)? Community driven input would be helpful for searching through constructs, especially when there are many similar options.

@dontirun we have talked about creating some sort of aggregate to indicate "popularity" or how active a project is in general. Something like a combination of github stars, # of recently closed issues, npm downloads, frequency of recent commits, etc.

If you're interested in this definitely feel free to do some research and let us know what you think would be the best strategy. My instinct is that we could compute this for each package while computing other metadata, like tags, and put it into the metadata where it will be added to the catalog to use for searching/sorting. So around here in the current code.

Another idea would be to add construct specific information into the cdk analytics metadata. However that could have some privacy concerns and there could be issues with max template size given the usage of many constructs.

This issue is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon. If you wish to exclude this issue from being marked as stale, add the "backlog" label.