badges/shields

Badge request: version for FreeBSD ports

Open

#1693 opened on May 19, 2018

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

Description

The easiest way to get the version number is to either query https://repology.org/ or https://www.freshports.org/.

I might work on this soon myself. However, if you'd like to do it yourself then go for it. 😄 😈

Contributor guide

Tech stack
javascriptnodejsrest api
Domain
backendapi
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
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.
clear
Prerequisites
Familiarity with Node.jsUnderstanding of Shields badge creationBasic HTTP request handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Look at existing badge implementations in the shields repository, particularly those that fetch data from external APIs (e.g., in `services/` directory). Determine how to query Repology or FreshPorts for FreeBSD port versions. Follow the pattern for adding a new service badge, including registering the route and adding tests. The issue has no assignee, so it is available for anyone to work on.