Fix credential hardcoded in source in Fastify

A credential appears as a literal in source. Anything committed is in the repository's history, in every clone, and in every build artefact, so removing the line later does not revoke it. Read secrets from the environment or a secret manager, and rotate anything that has been committed.

high likely Fastify CWE-798 / OWASP A07:2021

The vulnerable pattern in Fastify

HIGH likely Credential hardcoded in source A07:2021 src/billing.ts:2:20 1 │ // FIXTURE: hardcoded-secret - Stripe live key prefix. 2 │ const STRIPE_KEY = 'sk_l***' │ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ credential written into source 3 │ 4 │ export async function charge(amountCents: number) {

This finding comes from the Fastify fixture in the owlwarden test suite. This literal carries the prefix of a Stripe live secret key, so it is a real credential rather than a placeholder. It is in the repository's history and in every clone; deleting the line does not revoke it.

The corrected handler

Declare it in the @fastify/env schema so a missing value fails at boot.

await app.register(env, {
  schema: {
    type: 'object',
    required: ['API_KEY'],
    properties: { API_KEY: { type: 'string' } },
  },
})

If you are not using Fastify

Move the value into an environment variable or a secret manager, and rotate it - once committed it is in the history and in every clone, so removing the line does not revoke it.

Check your own repository

npx owlwarden scan
npx owlwarden explain hardcoded-secret

Runs on your machine. No account, no telemetry, no network unless you ask. In CI, SARIF uploads to code scanning and the exit code is the gate.

Other Fastify checks

Rules with a tested Fastify example.

hardcoded-secret for every framework / All rules / owlwarden