repo-scan

Analyze GitHub repository URLs for security risks and maintainer health.

77|13|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/KerberosClaw/kc_ai_skills --skill repo-scan-kerberosclaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-scan
Source: https://github.com/KerberosClaw/kc_ai_skills/tree/main/repo-scan
Command: npx skills add https://github.com/KerberosClaw/kc_ai_skills --skill repo-scan-kerberosclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub 開源專案安全掃描工具。輸入 GitHub repo URL,輸出專案概覽、靜態弱點分析、供應鏈風險、Issues 安全回報、維護者評估與風險總結。適用於安裝前的安全評估。

Core Features & Use Cases

  • 自動產出專案概覽、主要語言與風險點摘要
  • 靜態弱點分析與供應鏈風險評估
  • 針對 Issues 的安全回報整合與維護者健康度評估
  • Use case: 在安裝前快速評估任意 GitHub 專案的風險

Quick Start

在終端機執行 /repo-scan https://github.com/owner/repo 即開始安全評估。

Frequently Asked Questions about repo-scan

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

FAQPage Schema
How do I audit a GitHub repository for security risks before installing it?

To audit a GitHub repository for security risks, you can scan the repo URL to receive a project overview, static weakness analysis, supply chain risks, and maintainer health evaluation without executing any code.

What is the best way to check open-source maintainer health and supply chain risks?

Checking open-source maintainer health and supply chain risks involves analyzing repository metadata and issue reports to evaluate maintainer activity and identify potential vulnerabilities in the project dependencies.

Do I need git and gh CLI installed to perform a static analysis on a GitHub repo?

Yes, you need git and gh CLI installed to retrieve repository metadata and issue reports for a comprehensive security analysis, although the static checks themselves run without executing the project's code.

Can I evaluate GitHub issues for security reports using a dependency audit tool?

Yes, evaluating GitHub issues for security reports is possible by integrating issue retrieval with dependency audits to surface vulnerability reports and supply chain risks within the repository.

What limitations exist when running static analysis on a GitHub repository?

A limitation of running static analysis on a GitHub repository is that it assesses code weaknesses and supply chain risks without executing the code, meaning runtime vulnerabilities or dynamic execution issues are not captured in the output.