Switch to target compatibility with new reference implementation (zxcvbn-ts)

[cainlevy]

The original dropbox/zxcvbn library has aged considerably. Do you have any opinions around remaining faithful to v4.4.2 (circa 2017) or pinning to a new client-side reference implementation if community momentum manages to elect one?

[vanackere]

Indeed we could switch to a new reference client-side implementation since the dropbox/zxcvbn library looks unmaintained / not very active... Do you have any suggestion ?

[cainlevy]

zxcvbn-ts might be one to watch.

[vanackere]

Looking at it again a few month later: yes, it seems indeed like a good idea to switch to follow zxcvbn-ts instead.
However I don't have any time to work on this currently, so any contribution would be appreciated.

[patrykgz]

Looking at it again a few month later: yes, it seems indeed like a good idea to switch to follow zxcvbn-ts instead. However I don't have any time to work on this currently, so any contribution would be appreciated.

Could you provide some indication of what would be needed to match the new reference? As I understood it zxcvbn-ts only provides code optimization improvements rather than security or developer productivity ones.