Keep secrets out of Nuxt public runtime config
Sensitive credentials must not be exposed through runtimeConfig.public, which is visible to client bundles.
#Metadata
#Why it matters
Nuxt exposes runtimeConfig.public to the browser; placing secret material there leaks API keys, database passwords, and signing material to every visitor.
#Remediation
Keep secrets in the private runtimeConfig tree (non-public) and expose only publishable identifiers to the client after reviewing Nuxt runtime config documentation.
#Repository path
The generated metadata points to critiq-rules/libs/rules/catalog/rules/typescript/ts.security.nuxt-public-runtime-secret.rule.yaml.