fixing broken links

bump packages with npm audit
nhsbsa · Oct 1, 2024 · 50af87e · 50af87e
1 parent 0658ecd
commit 50af87e
Show file tree

Hide file tree

Showing 7 changed files with 24 additions and 27 deletions.
diff --git a/.github/workflows/broken-links.yml b/.github/workflows/broken-links.yml
@@ -14,9 +14,9 @@ jobs:
         with:
           url: "https://nhsbsa.github.io/nhsbsa-digital-playbook"
           buffer_size: 8192
-          exclude: "assets.nhs.uk/$ nhsbsauk.sharepoint.com www.baeldung.com docs.aws.amazon.com/ec2 www.pluralsight.com dps-gitlab.service.nhsbsa www.npmjs.com nhsbsa-digital-playbook/issues/new nhsbsa-digital-playbook/discussions/new owasp.org/www-project-secure-headers git-rewrite-scripts toolbox.hyperisland.com www.vic.gov.au"
+          exclude: "assets.nhs.uk/$ nhsbsauk.sharepoint.com www.baeldung.com docs.aws.amazon.com/ec2 www.pluralsight.com dps-gitlab.service.nhsbsa www.npmjs.com nhsbsa-digital-playbook/issues/new nhsbsa-digital-playbook/discussions/new owasp.org/www-project-secure-headers git-rewrite-scripts toolbox.hyperisland.com www.vic.gov.au www.udacity.com"
           max_connections: 20
           max_connections_per_host: 2
           timeout: 30
-          header: "User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0"
+          header: "User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:124.0) Gecko/20100101 Firefox/124.0"
 
diff --git a/package-lock.json b/package-lock.json
diff --git a/src/design/interaction-designer/training-resources.md b/src/design/interaction-designer/training-resources.md
@@ -57,7 +57,7 @@ Each role level in the framework includes a list of required skills. Each skill
 - [Service Design in Government](https://govservicedesign.net/)
 - [UX Scotland](https://uxscotland.net/)
 - [Design System Day](https://design-system.service.gov.uk/community/design-system-day/)
-- [Camp Digital](https://www.nexerdigital.com/campdigital/2024/)
+- [Camp Digital](https://www.nexerdigital.com/campdigital/archive/)
 - [Other UX / Design Conferences](https://docs.google.com/spreadsheets/d/1EmInflZQ7FTjsUoJi3tQm0AH1d70cGSxsBjNCEs2z2s/edit?usp=sharing)
 - [NHS England Bi-Weekly design huddle](https://app.mural.co/t/nhsdigital8118/m/nhsdigital8118/1704977856217/fbb56163e3235effa07acbae72671a6760e51942?sender=uc57e8beacae1be0dda5b2638)
 - [Gov Design System catchup (publicised in the X-Gov #govuk-design-system channel)](https://ukgovernmentdigital.slack.com/archives/C6DMEH5R6)

diff --git a/src/development/coding-naming-conventions.md b/src/development/coding-naming-conventions.md
@@ -169,7 +169,7 @@ The mainline branch should be named `main`. All branches should be `kebab-case`
 
 A single branch should be used per change/ticket.
 
-See [Git branching guidance](../dev-branching-git-branching/) for a more detailed explanation of Git branch naming
+See [Git branching guidance](../dev-git-branching-strategy/) for a more detailed explanation of Git branch naming
 
 :::
 ::: card

diff --git a/src/development/coding-quality-assurance.md b/src/development/coding-quality-assurance.md
@@ -28,5 +28,5 @@ The automated build will break for:
 * [SonarQube issue definitions][sonarqube_issues]
 * [SonarQube metric definitions][sonarqube_metric_definitions]
 
-[sonarqube_issues]: <https://docs.sonarqube.org/latest/user-guide/issues/>
-[sonarqube_metric_definitions]: <https://docs.sonarqube.org/latest/user-guide/metric-definitions/>
+[sonarqube_issues]: <https://docs.sonarsource.com/sonarqube/latest/user-guide/issues/introduction/>
+[sonarqube_metric_definitions]: <https://docs.sonarsource.com/sonarqube/latest/user-guide/code-metrics/metrics-definition/>
diff --git a/src/development/coding-securely.md b/src/development/coding-securely.md
@@ -69,16 +69,16 @@ Production code must be written with an understanding of common security risks a
 
 Production code must be written in accordance with good security practices as defined in the [OWASP top 10 proactive controls][owasp_top_ten_proactive_controls]
 
-* [C1: Define Security Requirements](https://owasp.org/www-project-proactive-controls/v3/en/c1-security-requirements)
-* [C2: Leverage Security Frameworks and Libraries](https://owasp.org/www-project-proactive-controls/v3/en/c2-leverage-security-frameworks-libraries)
-* [C3: Secure Database Access](https://owasp.org/www-project-proactive-controls/v3/en/c3-secure-database)
-* [C4: Encode and Escape Data](https://owasp.org/www-project-proactive-controls/v3/en/c4-encode-escape-data)
-* [C5: Validate All Inputs](https://owasp.org/www-project-proactive-controls/v3/en/c5-validate-inputs)
-* [C6: Implement Digital Identity](https://owasp.org/www-project-proactive-controls/v3/en/c6-digital-identity)
-* [C7: Enforce Access Controls](https://owasp.org/www-project-proactive-controls/v3/en/c7-enforce-access-controls)
-* [C8: Protect Data Everywhere](https://owasp.org/www-project-proactive-controls/v3/en/c8-protect-data-everywhere)
-* [C9: Implement Security Logging and Monitoring](https://owasp.org/www-project-proactive-controls/v3/en/c9-security-logging)
-* [C10: Handle All Errors and Exceptions](https://owasp.org/www-project-proactive-controls/v3/en/c10-errors-exceptions)
+* [C1: Define Security Requirements](https://top10proactive.owasp.org/archive/2018/c1-security-requirements/)
+* [C2: Leverage Security Frameworks and Libraries](https://top10proactive.owasp.org/archive/2018/c2-leverage-security-frameworks-libraries/)
+* [C3: Secure Database Access](https://top10proactive.owasp.org/archive/2018/c3-secure-database/)
+* [C4: Encode and Escape Data](https://top10proactive.owasp.org/archive/2018/c4-encode-escape-data/)
+* [C5: Validate All Inputs](https://top10proactive.owasp.org/archive/2018/c5-validate-inputs/)
+* [C6: Implement Digital Identity](https://top10proactive.owasp.org/archive/2018/c6-digital-identity/)
+* [C7: Enforce Access Controls](https://top10proactive.owasp.org/archive/2018/c7-enforce-access-controls/)
+* [C8: Protect Data Everywhere](https://top10proactive.owasp.org/archive/2018/c8-protect-data-everywhere/)
+* [C9: Implement Security Logging and Monitoring](https://top10proactive.owasp.org/archive/2018/c9-security-logging/)
+* [C10: Handle All Errors and Exceptions](https://top10proactive.owasp.org/archive/2018/c10-errors-exceptions/)
 
 ## References
 
@@ -96,4 +96,4 @@ Production code must be written in accordance with good security practices as de
 [ncsc_continually_test_your_security]: <https://www.ncsc.gov.uk/collection/developers-collection/principles/continually-test-your-security>
 [ncsc_plan_for_security_flaws]: <https://www.ncsc.gov.uk/collection/developers-collection/principles/plan-for-security-flaws>
 [owasp_top_ten_risks]: <https://owasp.org/www-project-top-ten/>
-[owasp_top_ten_proactive_controls]: <https://owasp.org/www-project-proactive-controls/>
+[owasp_top_ten_proactive_controls]: <https://top10proactive.owasp.org/>
diff --git a/src/research/research-tools-resources.md b/src/research/research-tools-resources.md
@@ -75,7 +75,6 @@ User researchers are also encouraged to look outside of the organisation for exi
 - [Laws of UX](https://lawsofux.com/)
 - [Open Design Kit from Bocoup](http://opendesignkit.org/)
 - [Service Design Toolkit](http://servicedesigntoolkit.org/)
-- [Design Research Techniques from CFC Mediala](http://designresearchtechniques.com/)
 - [uxdesign.cc – UX Design Methods & Deliverables](https://uxdesign.cc/ux-design-methods-deliverables-657f54ce3c7d)
 - [UX Mastery – UX Techniques](http://uxmastery.com/resources/techniques/)
 - [All about UX](http://www.allaboutux.org/)