badges/shields

macports version

Closed

#9,588 opened on Sep 19, 2023

View on GitHubContributor guide
 (11 comments) (1 reaction) (0 assignees)JavaScript (5,423 forks)batch import
good first issueservice-badge

Repository metrics

Stars
 (22,337 stars)
PR merge metrics
 (Avg merge 6d 3h) (71 merged PRs in 30d)

Description

📋 Description

I'd like to see a Version category badge for macports using its search interface at https://ports.macports.org.

🔗 Data

https://ports.macports.org/api/v1/ports/:package_name

It's achievable with a Dynamic JSON badge for now:

https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fports.macports.org%2Fapi%2Fv1%2Fports%2Fproxy-audio-device%2F&query=%24.version&label=macports

proxy-audio-device

🎤 Motivation

Shields has badges for several other package managers, and although I'm a fervent Homebrew user, I'd like to see macports supported, too.

Contributor guide

Research direction
Study the existing package manager badge implementations (e.g., Homebrew, npm) in the shields repository, then add a new service for macports using the provided API endpoint.
Tech stack
javascriptnodejs
Domain
devops
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.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70