Skip to content

Conversation

chakra-guy
Copy link
Collaborator

PR Title

  • A brief description of changes. If the PR has breaking changes add BREAKING:
    to the start of the PR title.

Description

Itemize the changes you have made into the categories below

  • BREAKING:

    • Describe the how to patch your code for the breaking changes
    • Create PRs for other projects with patches to breaking changes
  • FIXED:

    • Describe the fix/bug addressed
  • CHANGED:

    • Describe the change you have made to existing functionality
  • REMOVED:

    • Describe functionality removed and why
  • ADDED:

    • Describe functionality added and why
  • DEPRECATED:

    • Describe what was deprecated and why
  • SECURITY:

    • These should not be in a standard PR and addressed using the Security Advisory process

Checklist

  • Tests are included if applicable
  • Any added code is fully documented

Issue

Resolves #???

Copy link

socket-security bot commented Sep 26, 2025

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Added@​types/​pako@​2.0.41001007181100
Addedpako@​2.1.010010010078100

View full report

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.

1 participant