badges/shields

Badge request: Userscript version

Open

#829 opened on Nov 6, 2016

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (22,337 stars) (5,423 forks)batch import
good first issueservice-badge

Description

Since the dead of Userscripts.org a few years ago, a lot of script-writers moved their userscripts to GitHub. It would be great if there was a shield showing the @version 1 2 of an userscript. Other metadata would be great too. I also noticed that userscripts mostly don't live on the repos root, so navigating to the .user.js file should be part of the shield url.

Contributor guide

Tech stack
javascript
Domain
backendtooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaScriptShields.io APIregexGreaseMonkey metadata
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate how to fetch the raw .user.js file from a GitHub repository (or other host) and parse the @version line from its metadata block. Review existing badge patterns in the shields.io codebase (e.g., GitHub version badge) and adapt to parse regex for `// @version x.x.x`. Consider URL patterns that allow specifying a path to the .user.js file, as userscripts are often not in the root.