You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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 ?
vanackere
changed the title
any plans to target compatibility with new reference implementations?
Switch to target compatibility with new reference implementation (zxcvbn-ts)
Dec 10, 2021
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.
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.
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?
The text was updated successfully, but these errors were encountered: