Skip to content

v1.6.0 - HIBP severity fixed and stricter gates

Choose a tag to compare

@WhiteMuush WhiteMuush released this 15 Oct 07:17
· 113 commits to main since this release
15df567

HIBP breaches now get the severity they deserve, the dashboard widgets show every breach, and the codebase runs behind much stricter gates.

Upgrading

One migration runs on start: 20261014120000_canonical_hibp_data_classes renames the plural HIBP labels already stored (passwords, credit_cards, bank_account_numbers, social_security_numbers) to the names the severity rules expect, and raises the alerts those labels kept too low. It never lowers a severity and can run twice safely. Rolling back to 1.5.0 still works. Nothing to do by hand.

Coming from the 1.4.0 image: the 1.5.0 image was never published on Docker Hub, so this release also brings the 1.5.0 changes and its migration. Read the 1.5.0 notes first.

Environment variables, port and the Alpine image base are unchanged.

Fixes

  • HIBP severity: HIBP names its data classes in the plural, so passwords, credit cards, bank accounts and social security numbers were not seen as critical and their alerts stayed at MEDIUM. They are now mapped, and the migration corrects the existing data.
  • Dashboard widgets: the seven breach widgets left out breaches added by hand and breaches from a source that is no longer connected, so they disagreed with the counters above them. They now count every breach, and a widget set to one source still narrows to it.
  • Failed dashboard saves: a refused layout or view change looked saved and was lost on reload. A bar now says the change was not saved, with a Retry button.
  • Okta: a user without an email was stored with its login as the address. It is now kept only when it is a valid email.
  • Directory type check: a connection type such as toString was accepted as valid. Only the real types are accepted now.

Local development

  • make up and make db-up can run side by side, and make image builds and runs the production image on port 3001 to test it.
  • A public fictional demo dataset is seeded with make seed-dev.
  • The dev container runs as a non-root user (set APP_UID and APP_GID if yours is not 1000).
  • The dev app and database ports are bound to 127.0.0.1, so they are no longer reachable from the network. An existing local database container keeps its old binding until it is recreated.

Quality

  • make check now runs before every push: npm run check, the integration tests, a schema drift check against the migrations, and the production build.
  • npm run check adds gitleaks on the whole history, shellcheck, Trivy on the Dockerfiles, and a check of the commits on the branch. CI runs the same gates.
  • TypeScript noUncheckedIndexedAccess is on, and ESLint now rejects floating promises, misused promises and non-exhaustive switches.
  • Every code file is at most 200 lines, tests included, and every code comment is a single sentence.