security-hunter-ts

Audit TypeScript code for security vulnerabilities like hardcoded secrets and injection risks.

5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/skyosev/agent-skills --skill security-hunter-ts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-hunter-ts
Source: https://github.com/skyosev/agent-skills/tree/main/hunter-party-ts/security-hunter-ts
Command: npx skills add https://github.com/skyosev/agent-skills --skill security-hunter-ts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit TypeScript code for security vulnerabilities — hardcoded secrets, injection risks, missing input validation at trust boundaries, insecure defaults, auth gaps, sensitive data exposure, and unsafe patterns like eval or innerHTML.

Core Features & Use Cases

  • Detect hardcoded secrets and sensitive data in TypeScript code.
  • Identify injection risks, missing input validation, insecure defaults, and auth gaps.
  • Support security reviews before deployment and during onboarding of external integrations.

Quick Start

Audit a TypeScript codebase to identify secrets, trust-boundary issues, and insecure configurations before deployment.

Frequently Asked Questions about security-hunter-ts

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

FAQPage Schema
How do I audit TypeScript code for security vulnerabilities before deployment?

Identify TypeScript security vulnerabilities by scanning for hardcoded secrets, injection risks, unsafe patterns like eval or innerHTML, and missing input validation at trust boundaries during pre-deployment code reviews.

What types of injection risks and unsafe patterns should a TypeScript security audit detect?

A TypeScript security audit detects injection risks and unsafe patterns like eval or innerHTML, alongside missing input validation at trust boundaries, insecure defaults, authentication gaps, and sensitive data exposure.

Does this security audit check for missing input validation at trust boundaries in API surfaces?

Yes, the security audit evaluates API surfaces for missing input validation at trust boundaries, hardcoded secrets, authentication gaps, and insecure defaults to support security assessments of external integrations.

Can I review third-party integrations for hardcoded secrets and data exposure in TypeScript?

Review third-party TypeScript integrations to identify hardcoded secrets, sensitive data exposure, authentication gaps, and insecure defaults during external integration onboarding and security assessments.

What are the limitations of auditing TypeScript code for insecure defaults and authentication gaps?

Auditing TypeScript code for insecure defaults and authentication gaps targets static code patterns like eval or innerHTML and trust boundary validation, requiring manual verification of runtime behavior and external dependency configurations.