Skip to content

Conversation

@Kris-LIBIS
Copy link
Collaborator

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
  • package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Insertion of Sensitive Information Into Sent Data
SNYK-JS-ANGULARCOMMON-14135651
  671  

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.

@github-actions
Copy link

Code Review Agent (Python)\n

No Python files changed. Skipping analysis.

@github-actions
Copy link

AI Governance checks failed

Please fix the following before re-running checks:

  • Ensure PR body includes provenance fields:
    • Prompt
    • Model
    • Date
    • Author
    • No secrets/PII (checkbox)
  • Complete compliance checklist items required for your change type (transparency notice, DPIA, logging, kill-switch, risk classification, human oversight, security review, vendor GPAI review).
  • Add a rollback note if the change is risky (authz, data export, evaluation logic, etc.).

Helpful links:

After edits, push updates or re-run the workflow to validate.

@ErykKul ErykKul force-pushed the main branch 2 times, most recently from e25688c to ddf1f86 Compare January 8, 2026 08:49
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.

3 participants