code-check-security-regression

Detect security regressions in changed TanStack Start/Node/TypeScript code paths.

22|3|Updated Jul 28, 2024
One-click install
npx skills add https://github.com/webdevcody/go-mailing-list --skill code-check-security-regression
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-check-security-regression
Source: https://github.com/webdevcody/go-mailing-list/tree/main/.claude/skills/code-check-security-regression
Command: npx skills add https://github.com/webdevcody/go-mailing-list --skill code-check-security-regression

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams detect newly introduced application-security vulnerabilities that appear during fast iteration, such as secret leaks, unsafe webhook handling, SSRF, insecure file handling, XSS, unsafe redirects, and missing rate limits.

Core Features & Use Cases

  • Secret exposure regression checks: Verifies whether secret-like environment variables are logged or accidentally reach client bundles.
  • Webhook signature verification validation: Flags webhook handlers that process requests without verifying authenticity.
  • SSRF and unsafe fetch validation: Detects fetch/HTTP calls that may use user-controlled URLs without allowlisting.
  • Upload/download safety review: Looks for unsafe handling in upload/download paths, including traversal and missing constraints.
  • Dangerous rendering detection: Finds risky rendering patterns like dangerouslySetInnerHTML and unsafe innerHTML usage tied to user content.
  • Redirect and security header hygiene: Identifies open-redirect patterns and missing rel="noopener noreferrer" on target="_blank".
  • Abuse-prone endpoint rate limiting checks: Flags new public endpoints that may need rate limiting.

Quick Start

Run a Git diff–scoped security regression scan and review the ranked HIGH/MEDIUM/LOW findings, applying only the allowed mechanical auto-fixes.

Frequently Asked Questions about code-check-security-regression

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

FAQPage Schema
How do I scan Git diffs for security regressions like secret leakage and XSS?

Run a Git diff-scoped security regression scan on changed code paths to detect secret leaks, XSS, and unsafe fetch calls, outputting ranked HIGH, MEDIUM, and LOW findings for review.

What is a security regression scan and how does it handle webhook verification?

A security regression scan identifies newly introduced vulnerabilities in recent code changes, flagging webhook handlers that process requests without verifying authenticity signatures to prevent unauthorized access.

Does security regression scanning work with TanStack Start and TypeScript Node repositories?

Yes, this security regression scanning applies specifically to TanStack Start, Node, and TypeScript repositories, checking recent diffs for secrets in logs, client bundles, and unsafe server-side fetch calls.

How do I check changed code paths for SSRF and unsafe fetch calls?

Run a targeted detector that traces URLs to determine user control, flagging fetch and HTTP calls in changed code paths that use user-controlled URLs without allowlisting to prevent SSRF.

Can I find missing rate limiting on new public endpoints during code review?

Yes, scan recent diffs for abuse-prone endpoints to find missing rate limiting. The scan flags new public endpoints that may require rate limiting to prevent automated abuse.

What limitations exist when scanning for secret exposure in logs and client bundles?

Safe reporting is a key limitation; the scan avoids leaking literal secret values in its output. It checks if secret-like environment variables are logged or reach client bundles but masks the actual values.