Skip to main content

vulkro logout

Log out this device: delete the local device token and cached lease, then make a best-effort revoke call to the account server.

Local logout always succeeds. A failed or offline revoke is a warning, not an error.

After logging out the machine is on Free and keeps scanning; Pro needs signing in again with vulkro login. A perpetual offline .lic (if you installed one with vulkro activate) is left untouched and keeps working.

Usage​

vulkro logout

This command takes no arguments and no flags.

Exit codes​

  • 0 logged out (or nothing to do).
  • 2 local database error.

Command reference​

Generated from vulkro help logout on vulkro 0.26.0. This block is the authoritative flag, usage, and exit-code reference for this command; the prose above is the friendly explanation. Do not edit this block by hand; run npm run docs:cli after a release.

Sign this machine out of your Vulkro account.

Log out this device: delete the local device token and cached lease, then make a best-effort revoke call to the account server. Local logout always succeeds; a failed or offline revoke is a warning, not an error. After logout this device drops to the Free tier, so scanning, findings with their proof, and the fix keep working; only the Pro capabilities need `vulkro login` again. A perpetual offline `.lic` (if you installed one with `vulkro activate`) is left untouched and keeps working.

Exit codes: `0` logged out (or nothing to do); `2` local database error.

Usage: vulkro logout [OPTIONS]

Options:
      --offline
          Hard-disable every outbound network call for this run (sets VULKRO_OFFLINE=1). Blocks the CVE feed, the license heartbeat, the update check, webhooks, and any cloud AI endpoint; a loopback model (http://127.0.0.1, http://localhost) is still allowed. Equivalent to exporting VULKRO_OFFLINE=1, and the flag wins when both are set

  -h, --help
          Print help (see a summary with '-h')
Last updated on