Verify & CI

Once a configuration is saved, --verify checks that your project still matches the license you chose — that the LICENSE file is the official, up-to-date text, that every manifest's license field carries the right identifier, and, when you opted into them, that your source-file headers are present and current.

npx license-wizard --verify

By default, verification self-heals: anything out of sync — an edited copyright line, a stale LICENSE, a hand-changed manifest field, a source file missing its header — is brought back in line with the license you chose. When nothing has drifted, it confirms and exits zero.

Strict mode for CI

Add --strict to make any mismatch an error instead: License Wizard leaves everything untouched, lists each surface that drifted, and exits non-zero so the pipeline stops. A passing run exits zero, making it a drop-in check step. --strict only modifies a --verify run; supplied on its own it errors with a clear message rather than being silently ignored.

- name: Check the license is in sync
  run: npx license-wizard --verify --strict

Verification reads only your saved configuration — the .licensewizardrc.json file first, then the manifests. Both a LICENSE file and a saved configuration must exist, or it reports the problem and exits non-zero.