Skip to content

Conversation

annahassel
Copy link
Contributor

No description provided.

@annahassel annahassel force-pushed the fix/contact-update-username branch 2 times, most recently from deb47c0 to f96c611 Compare April 21, 2025 10:32
@annahassel annahassel changed the title fix(contact.verify-email): update username using metadata param fix(contact): update username using action param instead of config Apr 21, 2025
@annahassel annahassel force-pushed the fix/contact-update-username branch 2 times, most recently from 58998cf to d7b8c41 Compare May 16, 2025 08:22
@annahassel annahassel changed the title fix(contact): update username using action param instead of config feat: custom phone challenge rate limiter + contact update username using action param May 16, 2025
@annahassel annahassel force-pushed the fix/contact-update-username branch from d7b8c41 to a99da46 Compare May 16, 2025 09:37
@annahassel annahassel force-pushed the fix/contact-update-username branch from 969c6cd to f7e1b16 Compare September 4, 2025 10:58
Copy link

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
[email protected] has Obfuscated code.

Confidence: 0.94

Location: Package overview

From: pnpm-lock.yamlnpm/[email protected]

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

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.

1 participant