v12.1.1

Patch Changes

• #277 fc0efb9 Thanks @wKovacs64! - Recommend the interactive prompt of the apiKey command over providing your key as a command-line argument (for enhanced security) when the API responds with 401 Unauthorized.

• #274 50f59ec Thanks @wKovacs64! - Update conf to v13.0.1, ora to v8.0.1, and hibp to v14.1.2. The last one fixes 401 Unauthorized response handling, as the haveibeenpwned.com API (v3) changed its response format.

v12.1.0

Minor Changes

• #253 d80c130 Thanks @wKovacs64! - Provide an interactive prompt for the API key when the apiKey command is issued without an argument. This is a safer way to input your API key, as providing it on the command line may cause it to show up in your shell's command history.

v12.0.0

Major Changes

• #243 fd72c24 Thanks @wKovacs64! - Drop support for Node.js 16 as it is end-of-life, making the new minimum Node.js runtime v18.0.0. Please upgrade your Node.js environment if necessary, or continue using a previous release if you are unable to upgrade your environment.

Minor Changes

• #248 f75f0aa Thanks @wKovacs64! - Add new subStatus command to get the current subscription status of your HIBP API key. See https://haveibeenpwned.com/API/v3#SubscriptionStatus for more information.

• #247 37f3a6f Thanks @wKovacs64! - Add the --pad (-p) option to the pw command, allowing you to ask the remote API to add padding to the response to obscure the password prefix. See https://www.troyhunt.com/enhancing-pwned-passwords-privacy-with-padding/ for more information.

• #246 372b291 Thanks @wKovacs64! - Refresh the project logo.

v11.0.0

Major Changes

• 3fe2524 Thanks @wKovacs64! - Drop support for Node.js 14 as it is end-of-life, making the new minimum Node.js runtime v16.0.0. Please upgrade your Node.js environment if necessary, or continue using a previous release if you are unable to upgrade your environment.

v10.0.1

Patch Changes

• ae51440 Thanks @wKovacs64! - Write version bumps to package-lock.json.

v10.0.0

Major Changes

• 581d0dc4 and 1bd53262 Thanks @wKovacs64! - Drop support for Node.js 10 and 12 as they are both end-of-life, making the new minimum Node.js runtime v14.13.1. This also converts the project to pure ESM as it is fully supported in 14.13.1, 16 and beyond. Please upgrade your Node.js environment if necessary, or continue using the latest v9 release of pwned if you are unable to upgrade your environment.

v9.0.0

9.0.0 (2020-09-10)

Bug Fixes

• deps: update conf to v7 (#105) (35f652e)
• deps: update ora to v5 (#109) (5efbfae)
• deps: update yargs to v16 (#113) (e521b24)

chore

• node: drop Node 8 support (#88) (0fd12db)

BREAKING CHANGES

• node: This removes support for Node v8 and makes the new minimum runtime Node v10, as v8
  is EOL. Please upgrade your Node.js environment to at least version 10, or continue using the latest v8
  release of pwned if you are unable to upgrade your environment.

v8.0.1

8.0.1 (2019-09-22)

Bug Fixes

• deps: update ora to v4 (#72) (8fdec0b)

v8.0.0

8.0.0 (2019-07-20)

Bug Fixes

• deps: update hibp to v8 (#60) (ae2f30e)

Features

• api-v3: add apiKey command and pass API key to protected services (31ff873)
• api-v3: invert includeUnverified option default value (210f301)
• api-v3: invert truncate option default value (6a9826e)

BREAKING CHANGES

• api-v3: The includeUnverified option of the ba command now defaults to true, per
  Troy's recommendation. Although there are not many unverified breaches in the system, it's
  possible you will get more breaches back than you did previously. You may explicitly disable this
  by negating the value for this option.
• api-v3: The truncate option of the ba and search commands now defaults to true,
  per Troy's recommendation. If you do not negate it explicitly, each Breach result will only
  contain the breach name (no metadata).
• api-v3: Several of the haveibeenpwned.com services now require an API key from
  https://haveibeenpwned.com/API/Key. See Troy's blog post for rationale and a full explanation. Once you have obtained your API key, you must run "pwned apiKey <your-key>" to configure pwned so that it may use it in future requests made to protected endpoints. Some commands, like pw, do not require an API key and will continue to function without one. Thus, you may continue to use pwned without an API key, as long as you only care about the commands that do not require one. Each command indicates if it requires an API key in the help for the specific command.

v7.0.1

7.0.1 (2019-07-06)

Bug Fixes

• deps: update hibp to ^7.5.2 (0c55480)