dependencies

Catalog dependencies from manifests into a structured JSON report.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git-pkgs, and includes scripts (resource) components.

What problem does it solve?

Identify and catalog every dependency declared across manifests (package.json, Gemfile, go.mod, requirements.txt, etc.) in the repository.

Core Features & Use Cases

  • Comprehensive discovery across multiple manifests and ecosystems.
  • Structured output including manifest_path, ecosystem, name, and version constraints.
  • Use cases include license compliance, security auditing, and inventory for governance.

Quick Start

Run the script to index all dependency manifests and write the results to report.json.

Frequently Asked Questions about dependencies

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

FAQPage Schema
How do I inventory all dependencies declared across multiple manifests in a repository?

You can inventory dependencies by running the included wrapper script, which scans manifests like package.json and go.mod to extract names, ecosystems, version constraints, and paths into a structured JSON report for auditing.

What is the best way to generate a JSON report of repository dependencies for security auditing?

The best way to generate a JSON dependency report for security auditing is running the wrapper script, which parses manifests like requirements.txt and Gemfile to produce a structured inventory with names, versions, and paths for risk analysis.

Does this dependency indexing tool work with multiple package ecosystems like npm and Ruby?

Yes, this dependency indexing tool works across multiple ecosystems including npm, Ruby, Go, and Python by parsing their respective manifests like package.json, Gemfile, go.mod, and requirements.txt to catalog all declared dependencies.

Can I extract version requirements and manifest paths from package.json and go.mod files?

Yes, you can extract version requirements and manifest paths from package.json and go.mod files. The Skill identifies every declared dependency and catalogs its ecosystem, version constraints, and exact manifest file location.

Do I need git-pkgs to catalog dependencies from manifests like Gemfile and requirements.txt?

Yes, git-pkgs is required to run the scripts that index and catalog dependencies from manifests like Gemfile and requirements.txt, producing a structured JSON output for governance and license compliance.