auth-boundaries

Detect authentication and authorization vulnerabilities in codebase changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Shah-Aayush/pr-reviewer --skill auth-boundaries
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auth-boundaries
Source: https://github.com/Shah-Aayush/pr-reviewer/tree/main/shared-skills/security-axes/auth-boundaries
Command: npx skills add https://github.com/Shah-Aayush/pr-reviewer --skill auth-boundaries

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that your application's authentication and authorization checks are robust, identifying common security vulnerabilities such as token leakage, privilege escalation, and missing access controls.

Core Features & Use Cases

  • Comprehensive Security Checks: Detects missing authorization checks, indirect object references (IDOR), privilege escalation, token leakage, session fixation, impersonation, and MFA bypass.
  • Customizable Severity Levels: Flags issues with different severity levels, allowing you to prioritize and address critical vulnerabilities first.
  • Use Case: Activate this Skill on code changes that affect authentication or authorization to automatically identify potential security risks before they become a problem.

Quick Start

Scan your codebase for auth boundaries violations using the 'auth-boundaries' skill.

Frequently Asked Questions about auth-boundaries

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

FAQPage Schema
How do I scan my codebase for authentication and authorization vulnerabilities?

Scanning codebases for authorization vulnerabilities requires parsing code changes to identify missing access controls, token leakage, and privilege escalation using automated security pattern analysis.

What is an IDOR vulnerability and how do missing access controls affect authorization boundaries?

An IDOR vulnerability occurs when indirect object references lack authorization checks, allowing unauthorized access. Missing access controls compromise auth boundaries by enabling privilege escalation and impersonation.

Can I detect token leakage and session fixation in code changes before deployment?

Yes, detecting token leakage and session fixation in code changes is possible by analyzing security patterns within authentication mechanisms, flagging vulnerabilities with customizable severity levels before deployment.

Does this security analysis require access to the entire code repository?

Yes, this vulnerability scanning requires access to code repositories to parse and analyze code for security patterns, specifically targeting code changes that affect authentication and authorization mechanisms.

What is the best way to identify privilege escalation and MFA bypass issues during development?

The best way to identify privilege escalation and MFA bypass issues is to analyze authentication-related code changes, automatically flagging potential security risks with prioritized customizable severity levels.

Why should I run vulnerability scanning on code changes affecting authentication boundaries?

Running vulnerability scanning on code changes affecting authentication boundaries is necessary to automatically identify security risks like token leakage and IDOR before they become exploitable problems.