build(deps-dev): bump @yao-pkg/pkg from 5.16.1 to 6.9.0

[dependabot]

Bumps @yao-pkg/pkg from 5.16.1 to 6.9.0.

Release notes

Sourced from @​yao-pkg/pkg's releases.

Release 6.9.0

6.9.0 (2025-10-15)

Features

• bump fetch with node 22.20.0 and 24.10.0 support (73fcf64)

Release 6.8.0

6.8.0 (2025-10-07)

Features

• update @​yao-pkg/pkg-fetch to version 3.5.28 and tar-fs to version 3.1.1 (b994c6e)

Bug Fixes

• audit (47f662d)

Release 6.7.0

6.7.0 (2025-09-26)

Features

• bump fetch v3.5.25 with node 20.19.5, 22.19.0, and 24.8.0, special thanks to @​faulpeltz (7ce1085)

Documentation

• behavior of ignore on dotfiles (#170) (de1e819)
• instructions for injecting Windows exe metadata (#174) (14e7df0)

Release 6.6.0

6.6.0 (2025-07-19)

Features

• [email protected] with Node.js versions 20.19.4 and 22.17.1 (6a04030)

Documentation

• add guidance on unsupported architectures to README.md (#160) (c22e442)

Release 6.5.1

6.5.1 (2025-05-17)

... (truncated)

Changelog

Sourced from @​yao-pkg/pkg's changelog.

6.9.0 (2025-10-15)

Features

• bump fetch with node 22.20.0 and 24.10.0 support (73fcf64)

6.7.0 (2025-09-26)

Features

• bump fetch v3.5.25 with node 20.19.5, 22.19.0, and 24.8.0, special thanks to @​faulpeltz (7ce1085)

Documentation

• behavior of ignore on dotfiles (#170) (de1e819)
• instructions for injecting Windows exe metadata (#174) (14e7df0)

6.6.0 (2025-07-19)

Features

• [email protected] with Node.js versions 20.19.4 and 22.17.1 (6a04030)

Documentation

• add guidance on unsupported architectures to README.md (#160) (c22e442)

6.5.1 (2025-05-17)

Bug Fixes

• bump pkg-fetch to address issues related to mismatching shas (8f38df7)

6.5.0 (2025-05-15)

Features

• bump pkg-fetch with node v20.19.1 and v22.15.1 (3087561)

6.4.1 (2025-04-30)

Bug Fixes

• prefer module.isBuiltin when checking core modules (3a57036)

6.4.0 (2025-04-08)

Features

• bump [email protected] with node v18.20.8 and v22.14.0 (1a381eb)

... (truncated)

Commits

• cd7a545 Release 6.9.0
• 73fcf64 feat: bump fetch with node 22.20.0 and 24.10.0 support
• 8f77222 Release 6.8.0
• 328b11d fix: bump @​yao-pkg/pkg-fetch and audit fixes (#176)
• 5f59d6b Release 6.7.0
• 7ce1085 feat: bump fetch v3.5.25 with node 20.19.5, 22.19.0, and 24.8.0, special tha...
• 14e7df0 docs: instructions for injecting Windows exe metadata (#174)
• de1e819 docs: behavior of ignore on dotfiles (#170)
• a886214 Release 6.6.0
• 6a04030 feat: [email protected] with Node.js versions 20.19.4 and 22.17.1
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: Changed. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​yao-pkg/​pkg@​5.16.1 ⏵ 6.9.0			+1	+7

View full report

[socket-security]

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		@yao-pkg/[email protected] is a AI-detected potential code anomaly. Notes: The verify(local) function implements an environment- and version-sensitive self-check that uses a separate Node process to run a crafted VM-based diagnostic script. While not clearly malicious, the pattern resembles anti-tamper/environment fingerprinting logic that could be abused if the local executable or environment is controlled by an attacker. There is no evident data exfiltration or backdoor, but the mechanism’s reliance on internal VM caches and version offsets warrants caution and documentation, especially regarding tamper-resistance, error handling, and the potential for misbehavior in non-standard runtimes. Confidence: 0.72 Severity: 0.58 From: package-lock.json → npm/@yao-pkg/[email protected] → npm/@yao-pkg/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@yao-pkg/[email protected]. 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		@yao-pkg/[email protected] is a AI-detected potential code anomaly. Notes: The code involves dynamically executing JavaScript code using the vm.Script module and managing child processes to handle this execution. This approach is inherently risky as it allows for arbitrary code execution and has potential security implications if the input data is not properly sanitized. However, there are no explicit signs of malicious intent such as data theft or system damage. The main concerns are related to the potential misuse of dynamic code execution and process management, which could be exploited in a supply chain attack scenario. Confidence: 0.80 Severity: 0.65 From: package-lock.json → npm/@yao-pkg/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@yao-pkg/[email protected]. 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		@yao-pkg/[email protected] is a AI-detected potential code anomaly. Notes: The fragment implements a sophisticated packaging/assembly mechanism for bundling a virtual filesystem with optional native binaries. While legitimate in advanced packaging tools, the combination of dynamic prelude injection, on-disk binary manipulation (bak/overwrite), and environment-driven external binary installation creates meaningful supply-chain security risk. The absence of explicit exfiltration or hard-coded secrets does not mitigate the risk of hidden Payload/Code injection in a build pipeline. Recommend thorough provenance checks, strict controls around prebuild-install, explicit documentation of dynamic payload embedding, and integrity verification (signatures, hashes) of all artifacts involved. Confidence: 0.72 Severity: 0.60 From: package-lock.json → npm/@yao-pkg/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@yao-pkg/[email protected]. 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