Compliance postures fails with 500 error when not logged in - we should show the same error page like on the other pages

Repository metrics

Stars

144 stars (144 stars)

PR merge metrics

PR metrics pending (PR metrics pending)

Description

Contributor guide

Research direction

Investigate the compliance postures route handler in the Go backend. Reproduce the 500 error by accessing the URL while logged out. Compare with other routes that handle unauthenticated users gracefully. Identify where the 500 is thrown and how to return a proper error page instead.

Tech stack

go

Domain

backend

Issue type

Bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

2

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Clear

Prerequisites

GitGo

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

75