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

Resolve CodeQL alert 19 "Potentially unsafe external link" #6053

Closed
7 tasks done
Tracked by #5129
roslynwythe opened this issue Jan 3, 2024 · 8 comments · Fixed by #6371
Closed
7 tasks done
Tracked by #5129

Resolve CodeQL alert 19 "Potentially unsafe external link" #6053

roslynwythe opened this issue Jan 3, 2024 · 8 comments · Fixed by #6371
Assignees
Labels
Feature: Code Alerts good first issue Good for newcomers P-Feature: Communities of Practice https://www.hackforla.org/communities-of-practice role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours
Milestone

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Jan 3, 2024

Prerequisite

  1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page.
  2. Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.

Overview

We need to resolve the alert "Potentially unsafe external link" which appears in the CodeQL alert 19 by adding the attribute rel="noopener noreferrer"

Action Items

  • The following item is required for GitHub to establish tracking between this issue and the alert. No action is required. You may simply check the checkbox. If you do follow the link to learn more about CodeQL alerts, DO NOT DISMISS THE ALERT.
  • https://github.com/hackforla/website/security/code-scanning/19
  • Open the file pages/communities-of-practice.html in your IDE
  • On line 54, replace:
<a href='{{ leader.links.linkedin }}' target='_blank' title='Linkedin Profile'>

with

<a href='{{ leader.links.linkedin }}' target='_blank' title='Linkedin Profile' rel="noopener noreferrer">
  • Make changes only to this specific href as flagged by CodeQL no. 19.
  • Using Docker, check the page remains the same in mobile, tablet, and desktop views as on the current website (See 2 in the Resources/Instructions section below)

Merge Team

Resources/Instructions

  1. GitHub CodeQL documentation
  2. Webpage: https://www.hackforla.org/communities-of-practice
  3. This issue is part of Epic: Create issues to resolve CodeQL alerts 1- 24, 98 "Potentially unsafe external link" #5129
@roslynwythe roslynwythe added Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing role missing Complexity: Missing labels Jan 3, 2024

This comment was marked as resolved.

@roslynwythe roslynwythe added good first issue Good for newcomers role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers P-Feature: Communities of Practice https://www.hackforla.org/communities-of-practice size: 0.25pt Can be done in 0.5 to 1.5 hours Feature: Code Alerts Ready for Prioritization and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing role missing Complexity: Missing labels Jan 3, 2024
@ExperimentsInHonesty ExperimentsInHonesty added this to the 02. Security milestone Jan 22, 2024
@aidanwsimmons aidanwsimmons self-assigned this Feb 9, 2024

This comment was marked as outdated.

@aidanwsimmons aidanwsimmons removed their assignment Feb 9, 2024
@KuanHsienYEH KuanHsienYEH self-assigned this Feb 10, 2024

This comment was marked as outdated.

This comment was marked as outdated.

This comment was marked as resolved.

@junadkat32

This comment was marked as outdated.

@roslynwythe

This comment was marked as outdated.

@kmdeakers kmdeakers self-assigned this Feb 24, 2024
Copy link

Hi @kmdeakers, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Code Alerts good first issue Good for newcomers P-Feature: Communities of Practice https://www.hackforla.org/communities-of-practice role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours
Projects
Development

Successfully merging a pull request may close this issue.

6 participants