Update dependency halmos to v0.2.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
halmos	==0.1.14 -> ==0.2.0

---

Release Notes

a16z/halmos (halmos)

v0.2.0

Compare Source

What's Changed

Breaking changes

• feat: replace --symbolic-storage with enableSymbolicStorage(address) cheatcode by @​daejunpark in https://github.com/a16z/halmos/pull/355
• feat: empty initial network state by @​daejunpark in https://github.com/a16z/halmos/pull/352
• feat: reject multiple setup paths by @​daejunpark in https://github.com/a16z/halmos/pull/351
• perf: increase default assertion solving timeout from 1s to 1m by @​daejunpark in https://github.com/a16z/halmos/pull/368
• feat: deprecate --bytecode and --reset-bytecode by @​daejunpark in https://github.com/a16z/halmos/pull/350

New features

• feat: support for new cheatcode of generating calldata by @​daejunpark in https://github.com/a16z/halmos/pull/360
• feat: branching over symbolic call addresses by @​daejunpark in https://github.com/a16z/halmos/pull/349

Bug fixes and improvements

• perf: code fastpath scanning for valid jump destinations by @​karmacoma-eth in https://github.com/a16z/halmos/pull/348
• fix: failed() cheatcode error by @​daejunpark in https://github.com/a16z/halmos/pull/359
• fix: vm.etch() leaves storage uninitialized by @​karmacoma-eth in https://github.com/a16z/halmos/pull/363
• fix: manually solve dynamic array overflow conditions by @​daejunpark in https://github.com/a16z/halmos/pull/366

Full Changelog: a16z/halmos@v0.1.14...v0.2.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4469c3e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
pypi/halmos@0.2.0	eval, filesystem, shell, unsafe	0	941 kB	daejunpark, justin_gerard

🚮 Removed packages: pypi/halmos@0.1.14

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
AI-detected potential code anomaly	pypi/halmos@0.2.0	Notes: The code contains multiple potential security risks, including unauthorized file writes, command injection, information leakage, and code injection. It should be reviewed and modified to ensure proper input validation, sanitization, and secure handling of user input. The presence of 'eval' raises concerns about the safety and security of the code. Confidence: 0.80 Severity: 0.70	fv-requirements.txt	🚫
AI-detected potential code anomaly	pypi/halmos@0.2.0	Notes: The primary concern in this script is the download and execution of an external script without validation. This can introduce significant security risks as the content of the external script is not verified. The other operations, such as setting up a virtual environment and installing dependencies, are standard practices. Confidence: 0.90 Severity: 0.65	fv-requirements.txt	🚫

View full report↗︎

Next steps

What is an AI-detected potential code anomaly?

AI has identified unusual behaviors that may pose a security risk.

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.

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore pypi/halmos@0.2.0