dependents

Identify top runtime dependents for published packages and generate report.json.

Updated May 20, 2026
One-click install
npx skills add https://github.com/lukehinds/scrutineer-attest-test --skill dependents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependents
Source: https://github.com/lukehinds/scrutineer-attest-test/tree/main/skills/dependents
Command: npx skills add https://github.com/lukehinds/scrutineer-attest-test --skill dependents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies the top runtime dependents for every published package in the repository, providing a ranked shortlist to support exposure-analysis workflows.

Core Features & Use Cases

  • Dependent discovery across all published packages by querying the ecosystem.
  • Deduplicate dependents by purl to prevent duplicates across packages.
  • Generate report.json with a dependents array and schema.json for validation.

Quick Start

Run this skill after the packages skill has populated the package list to emit a report.json containing the dependents array.

Frequently Asked Questions about dependents

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

FAQPage Schema
What is runtime dependent exposure analysis for software packages?

Runtime dependent exposure analysis identifies the top packages depending on your published repository packages. It queries the ecosystem API, deduplicates dependents by purl, and generates a ranked shortlist in report.json to support exposure-analysis workflows.

How do I identify top dependents for all packages in my repository?

To identify top dependents, run this Skill after the packages skill has populated the package list. It queries the ecosystem API for per-package lookups, deduplicates dependents by purl, and emits a report.json containing the dependents array.

Do I need to populate a package list before running exposure analysis?

Yes, you must run the packages skill first to populate the package list. The dependents Skill operates across this published package list, querying the ecosystem API for runtime dependents and producing a ranked report.json.

Does dependent deduplication prevent duplicate entries across multiple packages?

Yes, dependent deduplication by purl prevents duplicate entries across packages. The Skill queries the ecosystem API for dependents of every published package and deduplicates the results by purl before generating the final report.json.

What's the best way to generate a report of package dependents for exposure analysis?

The best way to generate a dependents report is to run this Skill after the packages skill. It performs network requests to the packages API, deduplicates dependents by purl, and validates the final dependents array against schema.json.

What format does the dependents report use for validation?

The dependents report uses report.json containing the dependents array, validated against a schema.json file. This structure ensures the ranked shortlist of top runtime dependents is properly formatted for exposure-analysis workflows.