What it finds on a demo project

The CLI flags code that writes a password field to the database with no apparent hashing call.

SiteCMD CLI 2.0.0
Demo project: Signup endpoint
npx sitecmd audit .
SiteCMD Code Scan - .
Checked: November 9, 2026
Framework: Express
Issues: 1 total | critical 0 | high 1 | medium 0 | low 0

High (1)
- [Security · security] Possible password write without visible hashing - src/routes/signup.js:13

Your code passes? Now watch your site.

Join the waitlist

Use password hashing instead of reversible encryption

Use a slow password-hashing library with a salt for each password. OWASP's password storage guide explains the choice.

Choose between bcrypt and Argon2id for password hashing

OWASP recommends Argon2id with at least 19 MiB of memory, 2 iterations and 1 degree of parallelism. For a legacy system using bcrypt, it recommends a work factor of at least 10 and a 72-byte password limit. Tune the work for your deployment rather than copying a library default.

Verify stored passwords through the hashing library

Use the library's password verification function during sign-in. Don't compare the submitted password directly with a stored string. OWASP's authentication guide covers password comparison.

Frequently asked questions

Can I use SHA-256 to hash passwords?

No. OWASP says fast hashes such as SHA-256 let attackers make large numbers of guesses quickly, and recommends a slow algorithm such as Argon2id, bcrypt or PBKDF2.

Confirm you're a person