wrdn-authz

Detect authorization defects in route handlers, middleware, and ORM queries.

6|1|Updated Nov 23, 2023
One-click install
npx skills add https://github.com/gmcabrita/dotfiles --skill wrdn-authz-gmcabrita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrdn-authz
Source: https://github.com/gmcabrita/dotfiles/tree/main/.agents/skills/wrdn-authz
Command: npx skills add https://github.com/gmcabrita/dotfiles --skill wrdn-authz-gmcabrita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects authorization defects where the wrong principal, tenant, role, or scope boundary reaches protected data or actions.

Core Features & Use Cases

  • Surface IDORs, missing ownership/tenant scoping, and fail-open role/permission checks in code changes.
  • Guide reviewers through route handlers, middleware, decorators, resolvers, serializers, ORM queries, and token-derived claims across common frameworks.
  • Provide structured traces and concrete fixes to close authorization gaps during code reviews.

Quick Start

Inspect a diff and surface candidate authorization bypasses with actionable traces and recommended remediations.

Frequently Asked Questions about wrdn-authz

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

FAQPage Schema
How do I detect IDOR and missing tenant scoping in code changes?

Detect IDOR and missing tenant scoping by analyzing route handlers, middleware, decorators, and ORM queries to surface authorization bypass patterns where the wrong principal reaches protected data, complete with file traces and fixes.

What is an authorization defect in route handlers and middleware?

An authorization defect in route handlers and middleware occurs when the wrong principal, tenant, role, or scope boundary reaches protected data or actions due to missing ownership checks or fail-open permission validations.

How do I review RBAC and token-derived claims for authorization bypasses?

Review RBAC and token-derived claims by analyzing resolvers, serializers, and token-derived claims across multiple frameworks to identify fail-open role checks and provide concrete remediations with severity estimates.

Does this authorization analysis work with ORM queries and serializers across different frameworks?

Yes, authorization analysis works with ORM queries and serializers across common frameworks, examining them alongside route handlers and middleware to identify boundary violations and provide structured file and line traces.

What is the best way to surface fail-open role and permission checks during code review?

The best way to surface fail-open role and permission checks is to inspect code diffs by analyzing middleware, decorators, and resolvers to identify bypass patterns, generating severity estimates and concrete fixes to close authorization gaps.