skills.rest
lukehinds
lukehindsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

packages

Query registry APIs for repository packages and write metrics to report.json.

Updated May 20, 2026
Search Tags:#packages#report#version#lookup#registries#ecosystems
One-click install
npx skills add https://github.com/lukehinds/scrutineer-attest-test --skill packages-lukehinds
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: packages
Source: https://github.com/lukehinds/scrutineer-attest-test/tree/main/skills/packages
Command: npx skills add https://github.com/lukehinds/scrutineer-attest-test --skill packages-lukehinds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Look up every published package for a repository across registries and record key metrics.

Core Features & Use Cases

  • Query the packages API for a repository URL and collect per-package data such as name, ecosystem, latest_version, licenses, downloads, and dependency counts.
  • Normalize and emit a report.json under the packages key, conforming to the provided schema.
  • Use Case: Build a centralized Packages tab for a project to surface package metrics across ecosystems.

Quick Start

Query the packages API for the repository and write the results to report.json.

Frequently Asked Questions about packages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I aggregate package data across multiple registries for a repository?▼

To aggregate package data across registries, query the packages API with the repository URL to collect names, versions, licenses, downloads, and dependencies, then normalize the results into a report.json file.

What package metrics are tracked when looking up versions across ecosystems?▼

Looking up versions across ecosystems tracks per-package metrics including name, ecosystem, latest_version, licenses, download counts, and dependency counts, writing the collected data array to report.json.

Can I build a centralized Packages tab to surface package metrics across ecosystems?▼

Yes, you can build a centralized Packages tab by querying the registry API for a repository URL, collecting normalized package metrics, and emitting a structured packages array that conforms to a defined schema.

Does the package lookup process require network access to the registry API?▼

Yes, the package lookup process requires network access to the registry API to fetch per-package data such as versions, licenses, downloads, and dependency counts for the specified repository.

How do I normalize and report package lookup results to follow a specific schema?▼

To normalize and report package lookup results, collect the registry API data and emit a report.json file under the packages key, ensuring the output array conforms to the provided schema.json structure.

What is the best way to track names, versions, and licenses for published packages?▼

The best way to track names, versions, and licenses is to query the packages API for the repository URL, collect the per-package data across registries, and record the key metrics in a normalized report.json file.

Related Skills

Explore More Software Engineering Skills→
parcadeiparcadei
3.9k

nia-docs

Search package documentation and code examples across npm, PyPI, Crates, and Go modules.

Community
Advanced
peterfoxpeterfox
25

packagist

Searches and retrieves PHP package metadata, stats, and advisories from the Packagist API.

Community
Intermediate
Scaffold-StarkScaffold-Stark
109

stark-update-phase1

Analyze and validate Scaffold-Stark-2 dependency versions against live registry data.

Official
Advanced
haipham22haipham22
2

golang-pkg-go-dev

Retrieve Go package documentation, API signatures, versions, and vulnerabilities.

Community
Intermediate