Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: use string-timing-safe-equal package #939

Merged
merged 1 commit into from
Oct 24, 2024

Conversation

EvanHahn
Copy link
Contributor

This change should have no user impact.

I just published string-timing-safe-equal, a package that replaces our timingSafeEqual utility.

I think this is a useful change on its own but will make an upcoming server change smaller.

This change should have no user impact.

I just published [`string-timing-safe-equal`][0], a package that
replaces our `timingSafeEqual` utility.

I think this is a useful change on its own but will make an upcoming
server change smaller.

[0]: https://www.npmjs.com/package/string-timing-safe-equal
@EvanHahn EvanHahn requested a review from achou11 October 23, 2024 21:15
@awana-lockfile-bot
Copy link

package-lock.json changes

Click to toggle table visibility
Name Status Previous Current
string-timing-safe-equal ADDED - 0.1.0

@EvanHahn EvanHahn merged commit 03a2927 into main Oct 24, 2024
8 checks passed
@EvanHahn EvanHahn deleted the use-string-timing-safe-equal-package branch October 24, 2024 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants