security-review

Name: security-review
Availability: InStock
Author: sudocarlos

Audit Go modules, Dockerfile dependencies, and authentication flows for security vulnerabilities.

4|1|Updated Mar 13, 2026

Search Tags:#code review #security #vulnerability #audit #privacy #dependency scanning

Ready to run

npx skills add https://github.com/sudocarlos/tailrelay --skill security-review-sudocarlos

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/sudocarlos/tailrelay/tree/main/.agents/skills/security-review
Command: npx skills add https://github.com/sudocarlos/tailrelay --skill security-review-sudocarlos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires trivy, grype, govulncheck, docker, and includes references (resource) components.

What problem does it solve?

This Skill automates the process of identifying and mitigating security vulnerabilities within your codebase, dependencies, and container configurations, ensuring a robust security posture.

Core Features & Use Cases

Dependency Scanning: Audits Dockerfile dependencies and Go modules for known CVEs.
Code-Level Checks: Assesses authentication flows, input validation, and potential injection risks.
Privacy Assessment: Reviews data persistence and log sanitization for privacy compliance.
Use Case: Before deploying a new service, use this Skill to perform a comprehensive security review, identifying potential risks in dependencies, authentication mechanisms, and data handling.

Quick Start

Run a full security and privacy review of the tailrelay project.

Frequently Asked Questions about security-review

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

FAQPage Schema

How do I scan Go modules and Docker dependencies for known CVEs before deployment?▼

Performing a dependency vulnerability scan for Go modules and Docker configurations identifies known CVEs using tools like govulncheck, trivy, and grype. This process audits your project dependencies to mitigate security risks before deployment.

What does a comprehensive code-level security review cover for authentication and input validation?▼

A comprehensive code-level security review assesses authentication flows, input validation mechanisms, and potential injection risks. It evaluates how your code handles data persistence and log sanitization to ensure robust privacy and security compliance.

Do I need Docker installed to run an automated security and privacy review on my project?▼

Yes, Docker is required as a dependency to perform comprehensive security and privacy reviews, particularly for container hardening checks and Dockerfile dependency auditing. You also need trivy, grype, and govulncheck installed.

What is the best way to prevent data exfiltration and ensure privacy compliance in my codebase?▼

The best way to prevent data exfiltration and ensure privacy compliance is through an automated privacy assessment that reviews data persistence and log sanitization. This identifies potential data handling risks within your codebase.

Can I use trivy and grype together for container hardening and vulnerability scanning?▼

Yes, using trivy and grype together provides comprehensive vulnerability scanning and container hardening assessment. Both tools are integrated to audit Dockerfile dependencies and identify known CVEs across your software project.

When should I perform a security audit on my software dependencies and authentication mechanisms?▼

You should perform a security audit on dependencies and authentication mechanisms before deploying a new service. This identifies potential risks in dependency vulnerabilities, authentication flows, and data handling early in the lifecycle.