badges/shields

Badge request: Detailed badges for AUR

Open

#4656 opened on Feb 15, 2020

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

Description

:clipboard: Description

So much more info could be captured from AUR!

  • Popularity
  • Maintainer
  • Last Packager
  • Last Updater
  • Package base
  • Out-of-date or not
  • PKGBUILD Version

:link: Data

Same wasy as existing AUR badges.

:microphone: Motivation

I think it's cool. It's also informative. Let me know if you want help with this. I'd gladly implement all of the above.

Contributor guide

Tech stack
javascriptnodejs
Domain
backendapi
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-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with shields.io badge servicesUnderstanding of AUR APIBasic JavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Examine the existing AUR badge implementation in the shields.io codebase (likely in services/aur/). Understand the pattern for fetching data from the AUR API and generating badges. Implement new badge endpoints for each of the requested fields (popularity, maintainer, etc.) following the same pattern. Ensure to handle cases where data may be missing. Check any existing comments or discussions on this issue for additional guidance.