github-repo-analyzer

Analyze GitHub repositories for license compatibility and Trivy security findings.

1|1|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/growmax/growmax-skills --skill github-repo-analyzer-growmax
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-repo-analyzer
Source: https://github.com/growmax/growmax-skills/tree/main/skills/github-repo-analyzer
Command: npx skills add https://github.com/growmax/growmax-skills --skill github-repo-analyzer-growmax

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires trivy, and includes scripts (resource) and references (resource) components.

What problem does it solve? Evaluating a third-party GitHub repository before adoption requires manually checking its license terms, dependency vulnerabilities, hardcoded secrets, and maintenance health, which is slow and error-prone when done from memory. ## Core Features & Use Cases - License Detection & Verdict: Fetches the actual LICENSE text (robust to GitHub API rate limits via raw file fallback), classifies it into categories like permissive, copyleft, or source-available, and issues a compatibility verdict for a commercial closed-source SaaS. - Trivy Security Scan: Runs trivy repo to bucket CVEs, secrets, and IaC misconfigurations by severity, with conservative thresholds producing a safe / caution / unsafe verdict; can also parse an existing CI-generated Trivy JSON report offline. - Adoption Briefing: Produces a structured Markdown briefing covering what the project is, the problem it solves, maintenance pulse, external reviews, and a combined license-plus-security verdict. - Use Case: A teammate pastes a GitHub URL and asks "can we use this at Growmax?" — the skill returns a snapshot table, severity counts, license obligations, and one bottom-line recommendation. ## Quick Start Analyze the GitHub repository at https://github.com/owner/repo and tell me whether it is safe for us to adopt, including its license and any vulnerabilities.

Frequently Asked Questions about github-repo-analyzer

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

FAQPage Schema
How do I check if a GitHub repo is safe to use in a commercial product?▼

Run the analyzer on the repo URL to get a two-axis verdict: license compatibility and security. The license axis classifies the LICENSE text into categories like permissive or copyleft, while the security axis runs a Trivy scan for CVEs, secrets, and misconfigurations.

How to scan a GitHub repository for vulnerabilities with Trivy?▼

Run scripts/security_scan.py with the repo URL, which executes trivy repo with vuln, secret, and misconfig scanners. It prints severity-bucketed counts, top findings, and a verdict; Trivy must be installed and needs network access to its vulnerability database.

Does the license detection work when the GitHub API is rate-limited?▼

Yes. The fetch script treats the GitHub API as best-effort enrichment and always detects the license from the actual LICENSE text fetched over raw.githubusercontent.com, which is not subject to the same rate limit.

Can I use an existing Trivy report instead of running a new scan?▼

Yes. Pass --parse with the path to an existing Trivy JSON report, for example one produced by your CI pipeline. This mode needs neither Trivy installed nor network access.

Why does a clean Trivy scan not guarantee a repo is secure?▼

Trivy only detects known CVEs, detectable secrets, and known misconfiguration rules. A clean scan says nothing about logic bugs, supply-chain compromise, or undisclosed vulnerabilities, so it is necessary but not sufficient.

What happens if a repository has no LICENSE file?▼

The skill reports the category as none, meaning all rights reserved by default. Without a license you have no legal right to use, copy, or modify the code, so the verdict is to avoid it or ask the author to add a license.