Avoid hardcoded auth secrets
JWT, session, and strategy secrets should not be embedded directly in source code.
#Metadata
#Why it matters
Hardcoded auth secrets are hard to rotate and are exposed whenever the codebase or build artifacts leak.
#Remediation
Load the secret from environment-backed configuration or a secret manager and rotate the exposed value.
#Repository path
The generated metadata points to critiq-rules/libs/rules/catalog/rules/typescript/ts.security.hardcoded-auth-secret.rule.yaml.