Skip to content

chore: update versions#657

Open
github-actions[bot] wants to merge 1 commit intomasterfrom
changeset-release/master
Open

chore: update versions#657
github-actions[bot] wants to merge 1 commit intomasterfrom
changeset-release/master

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Mar 6, 2026

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

@nodesecure/rc@5.5.0

Minor Changes

@nodesecure/scanner@10.5.0

Minor Changes

Patch Changes

@nodesecure/tarball@3.6.0

Minor Changes

  • #656 fbc6023 Thanks @fraxken! - Export/Expose DependencyCollectableSet from tarball API entry

Patch Changes

@nodesecure/tree-walker@2.6.0

Minor Changes

@github-actions github-actions bot force-pushed the changeset-release/master branch 4 times, most recently from 0690843 to bfbdd29 Compare March 11, 2026 15:03
@github-actions github-actions bot force-pushed the changeset-release/master branch from bfbdd29 to ebf58db Compare March 14, 2026 15:35
@socket-security
Copy link

socket-security bot commented Mar 14, 2026

@github-actions github-actions bot force-pushed the changeset-release/master branch from ebf58db to 3ea850e Compare March 17, 2026 18:48
@socket-security
Copy link

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
License policy violation: npm @tsd/typescript

License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/typescript/ThirdPartyNoticeText.txt)

From: ?npm/@tsd/typescript@5.9.3

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@tsd/typescript@5.9.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
License policy violation: npm typescript

License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

From: ?npm/@arethetypeswrong/cli@0.18.2npm/typescript@5.6.1-rc

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@5.6.1-rc. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

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.

0 participants