Resolve "Potentially unsafe external link" for LA Incubator in `_includes/about-page/about-card-sponsors.html`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- docker, html, javascript, jekyll
Research direction
Open _includes/about-page/about-card-sponsors.html and add the specified rel="noopener noreferrer" attribute to the LA Incubator link. Using Docker, check the /about page in mobile, tablet, and desktop views, then confirm the link still works and opens as expected. When complete, check off the corresponding item in #5129.
Written by the indexing model from the issue text.
Description
Prerequisite
- 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.
- 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 fix a potentially unsafe external link by adding the attribute rel="noopener noreferrer". The problem and solution are similar to those detailed in the CodeQL alerts tracked in #5129; however, the instance addressed by this issue did not result in a CodeQL alert.
Action Items
- Open the file
_includes/about-page/about-card-sponsors.htmlin your IDE - Replace
<a href="https://laincubator.org" target="_blank" alt="LA Incubator">
with
<a href="https://laincubator.org" target="_blank" alt="LA Incubator" rel="noopener noreferrer">
- Using Docker, check the
/aboutpage and confirm that the page remains the same in mobile, tablet, and desktop views as on the current website. - Confirm that the LA Incubator link still works and opens as expected.
Merge Team
- When this issue is completed, check off the corresponding item in #5129
Resources/Instructions
- GitHub CodeQL documentation
- Webpage: https://www.hackforla.org/about/
- This issue is part of #5129
- Dominant language
- JavaScript
- Stars
- 364
- Forks
- 871
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 13
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hackforla/website
-
Feature: Code Alerts good first issue P-Feature: Project Info and Page role: back end/devOps role: front end size: 0.25pt
Difficulty 1/5 Under an hour Newbie friendliness 90/100
hackforla/website#8825 · 1 comment ·
Maintainers usually reply within 1 day
-
Feature: Code Alerts good first issue P-Feature: Project Info and Page role: back end/devOps role: front end size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Complexity: Small non-PR contribution P-Feature: Projects page ready for merge team role: back end/devOps size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
good first issue P-Feature: Project Info and Page P-Feature: Projects page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt time sensitive
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
ER: [Toolkit Page]: Fix "undefined" message shown when filter selects no guide or resource cardsOpenComplexity: Large ER needs issue: large non-PR contribution P-Feature: Toolkit Ready for Prioritization role: front end size: 1pt
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
hackforla/website#8819 · 2 comments ·
Maintainers usually reply within 1 day
All issues in hackforla/website
Similar issues
-
Code Cleanup Dev Environment
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ProjectSidewalk/SidewalkWebpage#5699 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
zenstackhq/zenstack#2873 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Jason-Vaughan/TangleClaw#2195 ·
Maintainers usually reply within 1 day
-
permissions in review update icon/data
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
simple-icons/simple-icons#15062 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-cao#16664 ·
Maintainers usually reply within 1 day