Create a badging tool for modules
See original GitHub issueSimilar to coveralls or travis, now that we have all the vulnerabilities information from npm modules automated, we can create a badging system similar to the one from coveralls so that we can issue badges for the README.md
on whether they have any vulnerability on the security-wg or not.
Not 100% sure about this but I think it is an idea worth exploring.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:10 (9 by maintainers)
Top Results From Across the Web
How do I add badges to Modules?
The Badgr External Tool is located within your Modules or your Course ... Select a badge you already created; Or, create a new...
Read more >Creating a badging system in Canvas - Adams Center
Go to your course in Canvas, go to settings, and then “apps,” search for “badgr” and then choose “Badgr US” and add it....
Read more >Badging | Tools, Publications & Resources
Center for the Future of Libraries Trend Badging. ... creating modules where students earn badges for individual skills (research, citation formatting, etc.) ...
Read more >Using Badging for Engagement - eCampusOntario Pressbooks
Badges have been used mainly as a motivation tool (complete this activity to earn a ... To create a brand new badge for...
Read more >Digital Badges: The New Digital Education Currency
Badges are the new education currency. In this article, learn 6 reasons why online course creators should use digital badges.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
So if no one else has any other objection, I will close this issue in a couple of days.
I think if we do something like this then it has to be an officially supported (from our/the foundation side), production-ready service and properly maintained. It’s easy and tempting to spin up lambdas for this or whatever, but taking it seriously in terms of pushing it to other repos and creating awareness means that this service shouldn’t incur down-times or somehow become un-maintained after 3 months - it will not be very professional of us.