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.

Sign up for GitHub

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

Jump to bottom

Delete http/takeovers/vercel-takeover.yaml #10159

Merged
merged 2 commits into from
Jul 1, 2024
Merged

Delete http/takeovers/vercel-takeover.yaml #10159

merged 2 commits into from
Jul 1, 2024

Conversation

DhiyaneshGeek
Copy link
Member

Template / PR Information

  • Fixed CVE-2020-XXX / Added CVE-2020-XXX / Updated CVE-2020-XXX
  • References:

Template Validation

I've validated this template locally?

  • YES
  • NO

Additional Details (leave it blank if not applicable)

Additional References:

@DhiyaneshGeek DhiyaneshGeek self-assigned this Jul 1, 2024
@DhiyaneshGeek DhiyaneshGeek added the Done Ready to merge label Jul 1, 2024
@github-actions github-actions bot requested a review from pussycat0x July 1, 2024 04:05
@DhiyaneshGeek DhiyaneshGeek linked an issue Jul 1, 2024 that may be closed by this pull request
vercel-takeover.yaml is a false positive template #10076
Closed
@ritikchaddha ritikchaddha merged commit a72fb2b into main Jul 1, 2024
3 checks passed
@ritikchaddha ritikchaddha deleted the non-vulnerable-vercel branch July 1, 2024 05:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@pussycat0x pussycat0x Awaiting requested review from pussycat0x

Assignees

@DhiyaneshGeek DhiyaneshGeek

Labels
Done Ready to merge
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

vercel-takeover.yaml is a false positive template
2 participants
@DhiyaneshGeek @ritikchaddha