Find your next open-source project

Search by name, purpose, or keyword — or paste a GitHub repository URL
All skills

api-security-best-practices

Review an API route from token check through authorization, input validation, and abuse limits.

When to use it

You have a protected endpoint or a failing route and need to confirm callers can't reach another user's or tenant's data.

For example

You say

Use api-security-best-practices to review my Express PATCH /users/:id profile update route, which takes a string ID and a display name.

You get
  • Route policy summary
  • Reproduced failure cases
  • Remaining gaps list

How it works

  • Checks are run against your own app: bad tokens, partial IDs, extra fields, and cross-tenant access.
  • Keeps your existing identity provider and data model instead of adding a second auth system.
  • Rate limits are treated as abuse control, not DDoS protection.