Skip to content

[Snyk] Security upgrade lighthouse from 6.5.0 to 7.3.0 - #30

Open
trabab wants to merge 1 commit into
masterfrom
snyk-fix-aa89fd25d2d9db90dffcb2a92119c4ba
Open

trabab wants to merge 1 commit into
masterfrom
snyk-fix-aa89fd25d2d9db90dffcb2a92119c4ba

Conversation

@trabab

@trabab trabab commented Sep 7, 2026

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • package.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Improper Verification of Cryptographic Signature
SNYK-JS-NODEFORGE-19635204
  721  

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-NODEFORGE-19635204
@trabab

trabab commented Sep 7, 2026

Copy link
Copy Markdown
Owner Author

Merge Risk: High

This major version upgrade to Lighthouse v7 introduces significant breaking changes, primarily for programmatic users of the Node API. The performance scoring algorithm has also been updated, which can affect reported scores.

Breaking Changes:

  • Node API: The main lighthouse function signature has changed. The second argument is now an options object where CLI flags (like port) are passed, and the third config argument has been removed. Configuration should now be passed as a property on the options object.
  • Performance Score: The weighting of metrics in the performance score has been updated (Performance v7). Total Blocking Time (TBT) and Cumulative Layout Shift (CLS) now have increased weight. This will likely change your performance scores even without any changes to your site.
  • Lighthouse Result (LHR) Object: The initial-url property at the root of the LHR object has been replaced by requestedUrl.

Recommendation:
If you are using Lighthouse programmatically via the Node module, you must update your code to match the new function signature. All users should be aware that performance scores will change due to the new metric weighting and should re-baseline their performance measurements.

Source: Lighthouse 7.0.0 Release Notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

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.

2 participants