chore(deps): Bump trycmd from 1.2.0 to 1.2.1

[dependabot]

Bumps trycmd from 1.2.0 to 1.2.1.

Commits

• b568bcd chore: Release
• 9bcd55c Merge pull request #459 from epage/deps
• 67c1cd1 chore: Move automod to dev-deps
• 00732af chore(deps): Update Rust Stable to v1.97 (#458)
• 9c3ccf6 style: Make clippy happy
• e95df8a Merge pull request #457 from epage/cargo
• 08ad9ba docs(snap): Fix bounds on cargo env support
• 5ab36e8 Merge pull request #456 from epage/docs
• dda19ac docs(snap): Call out adapters
• 718b87c docs(snap): Call out snapshots earlier
• 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 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)

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​wit-bindgen@​0.56.0
	cargo/​wit-component@​0.246.2
	cargo/​trycmd@​1.2.0 ⏵ 1.2.1

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. It is recommended to resolve "Warn" alerts too. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Potential code anomaly (AI signal): cargo trycmd is 85.0% likely to have a medium risk anomaly Notes: This is a legitimate testing utility with dangerous file system capabilities. While not malware, it poses significant security risks due to unrestricted file read/write operations that could be exploited if environment variables are controlled by an attacker. Confidence: 0.85 Severity: 0.65 From: Cargo.lock → cargo/trycmd@1.2.1 ℹ 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 support@socket.dev. 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 cargo/trycmd@1.2.1. 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		Filesystem access: cargo bstr Location: Package overview From: ? → cargo/trycmd@1.2.1 → cargo/bstr@1.13.0 ℹ Read more on: This package | This alert | What is filesystem access? 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: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/bstr@1.13.0. 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