BLOCKER

core/missing-auth-check

Auth checks on every server action / API route / service endpoint — not only in the UI layer or at the gateway.

Decided by
review judgement
Severity means
must not merge. The output contract
Applies to
every file — the core standard is not scoped by stack
Reaches
19 profiles: fullstack-react-node, infra-terraform, javascript-typescript, javascript-typescript-browser, mobile-android, mobile-ios, mobile-react-native, service-dotnet, service-express, service-go, service-java, service-node, service-python, typescript-effect, web-angular, web-nextjs, web-react, web-svelte, web-vue
Defined in
standards/core.md:72

Read it in the terminal

The same facts, from the checkout you are already in — no browser, and no network.

terminal
$ npx redlinegate explain core/missing-auth-check

Where this came from

You are most likely here from a review comment. A finding names its rule and, when your repository has told Redline where the standard is published, its address:

on the pull request
Redline/BLOCKER [core/missing-auth-check]: …
  → …/r/core/missing-auth-check

That second line is written by redline init --docs-url and is empty until an organisation sets one — there is no default, because a link to somebody else's copy of the standard is worse than no link. See Onboard a repository.

In context

This is a core rule: it applies in every profile, and every stack extends it rather than overriding it. The core standard lists it beside everything else a reviewer is asked to consider.

Other BLOCKER rules in this stack