Configuration files

License Wizard can remember your license choice so later runs start from a known default and verification has something to check against. Configuration is read from one of two places, in order of precedence:

• .licensewizardrc.json in the project root.
• The license-wizard field of package.json — the fallback when no rc file is present.

The saved config holds the license id, any copyright field values, and — when you opted into source-file headers — the header style, which is what tells --verify to check that surface:

{
  "licenseId": "Apache-2.0",
  "tokens": {
    "[yyyy]": "2026",
    "[name of copyright owner]": "Erdem Bircan"
  },
  "headers": { "style": "full" }
}

Saving is opt-in. In the wizard, choose to remember your selection; in a script, pass exactly one --save-* flag — --save-rc, --save-npm, or --save-composer. Saving writes to one location and clears the configuration from the others, so there's only ever one source of truth.