A session/auth cookie is set with Hono's setCookie(c, name, value, ...) helper WITHOUT the Secure flag, or with secure/httpOnly explicitly disabled.
Why AI tools produce this: AI coding tools produce this regularly, typically when prompted for a shortcut or a quick fix.
Why this matters
Missing Secure lets the browser send the cookie over plain HTTP where a network attacker can capture it (CWE-614); httpOnly: false exposes it to document.cookie, so any XSS on the origin can steal the session (CWE-1004).
Harden every auth cookie: setCookie(c, 'session', value, { httpOnly: true, secure: true, sameSite: 'Lax' }) If you genuinely need insecure cookies in dev, gate the value on the environment rather than hard-coding secure: false.
Suppressing this rule
If a finding is a genuine false positive, scope the suppression to the exact line and leave a reason, never disable the rule project-wide. Disable directives are line-scoped by design.
// oauthlint-disable-next-line auth.hono.cookie-insecure -- <reason>