xcrypto-scan

Scan go.mod files for outdated golang.org/x/crypto versions and advisories.

2|Updated Jul 8, 2024
One-click install
npx skills add https://github.com/redhat-best-practices-for-k8s/telco-bot --skill xcrypto-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xcrypto-scan
Source: https://github.com/redhat-best-practices-for-k8s/telco-bot/tree/main/.claude/skills/xcrypto-scan
Command: npx skills add https://github.com/redhat-best-practices-for-k8s/telco-bot --skill xcrypto-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify direct golang.org/x/crypto usage across repositories, surface outdated versions, and surface security advisories to enable proactive remediation.

Core Features & Use Cases

  • Scan direct golang.org/x/crypto dependencies in go.mod files across repositories.
  • Identify outdated versions with known security vulnerabilities and surface GitHub advisories.
  • Optional: create tracking issues in affected repos to drive remediation and visibility.

Quick Start

Run the xcrypto-lookup script with optional flags to scan for x/crypto usage across all tracked repositories.

Frequently Asked Questions about xcrypto-scan

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

FAQPage Schema
How do I scan Go repositories for golang.org/x/crypto dependencies?

To scan Go repositories for golang.org/x/crypto dependencies, this Skill parses go.mod files across GitHub organizations to track direct usage and identify specific versions in your projects.

How do I find outdated x/crypto versions with known security advisories?

Finding outdated x/crypto versions with known security advisories involves comparing parsed go.mod versions against tracked GitHub advisories to surface vulnerable dependencies for proactive remediation.

Can I automatically create GitHub issues for vulnerable x/crypto dependencies?

You can automatically create GitHub issues for vulnerable x/crypto dependencies using the optional issue creation flag in the xcrypto-lookup script to drive remediation visibility in affected repositories.

What is the best way to track x/crypto usage across a large fleet of Go projects?

Tracking x/crypto usage across a large fleet of Go projects is done by scanning go.mod files across GitHub organizations to identify direct dependencies and surface outdated versions.

Does the x/crypto scanner require any external dependencies to run?

The x/crypto scanner requires no external dependencies, leveraging a Bash-based xcrypto-lookup script to parse go.mod files and compare versions against advisories.

Why does the scanner only identify direct x/crypto usage in go.mod files?

The scanner identifies direct x/crypto usage in go.mod files to precisely surface outdated versions and advisories for the specific dependencies your projects explicitly declare.