Update dependency halmos to v0.1.14 and Python to 3.11

[renovate]

This PR contains the following updates:

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

---

Release Notes

a16z/halmos (halmos)

v0.1.14

Compare Source

What's Changed

halmos.toml configuration

• feat: enhance configuration management by using toml configuration file by @​pillip in https://github.com/a16z/halmos/pull/296
• feat: toml config, take 2 by @​karmacoma-eth in https://github.com/a16z/halmos/pull/298
• docs: example halmos.toml by @​karmacoma-eth in https://github.com/a16z/halmos/pull/299

Docker images

• feat: use docker image to load solvers and setup the testing environment by @​EmperorOrokuSaki in https://github.com/a16z/halmos/pull/295
• feat: solvers package by @​karmacoma-eth in https://github.com/a16z/halmos/pull/302
• ci: run workflow using solvers as a base image by @​karmacoma-eth in https://github.com/a16z/halmos/pull/307
• ci: add intermediary halmos-builder image and dockerize more workflows by @​karmacoma-eth in https://github.com/a16z/halmos/pull/308

Cheatcode/opcode support

• feat: support for forge-std assert cheatcodes by @​daejunpark and @​EmperorOrokuSaki in https://github.com/a16z/halmos/pull/323
• feat: support vm.getBlockNumber cheatcode by @​pillip in https://github.com/a16z/halmos/pull/325
• feat: functional implementation of EXTCODEHASH and EXTCODECOPY by @​karmacoma-eth in https://github.com/a16z/halmos/pull/328
• feat: add support for prank(sender, origin) and startPrank(sender, origin) cheatcodes by @​karmacoma-eth in https://github.com/a16z/halmos/pull/336

UX improvements

• feat: parse symbols from build to print readable traces by @​pillip in https://github.com/a16z/halmos/pull/309
• feat: trace rendering: extract selector from calldata by @​karmacoma-eth in https://github.com/a16z/halmos/pull/339
• feat: add ERC-1155 token receiver hooks as defaults in unknown call resolution by @​pcaversaccio in https://github.com/a16z/halmos/pull/291
• fix: handle solidity files with no contracts by @​karmacoma-eth in https://github.com/a16z/halmos/pull/333
• fix: simplify symbol parsing by @​karmacoma-eth in https://github.com/a16z/halmos/pull/334
• cli: deprecated --solver-parallel by @​daejunpark in https://github.com/a16z/halmos/pull/314

Performance improvements

• perf: chunk based memory model by @​karmacoma-eth in https://github.com/a16z/halmos/pull/288
• perf: optimize execution loop by @​karmacoma-eth in https://github.com/a16z/halmos/pull/293
• feat: cache unsat queries using unsat core by @​daejunpark in https://github.com/a16z/halmos/pull/311
• perf: prune infeasible paths early by @​daejunpark in https://github.com/a16z/halmos/pull/319
• perf: early exit for fail() by @​daejunpark in https://github.com/a16z/halmos/pull/322
• perf: abstract multiplication by @​daejunpark in https://github.com/a16z/halmos/pull/340

Bugfixes

• fix: smt encoding for evm div-by-zero by @​daejunpark in https://github.com/a16z/halmos/pull/271
• fix: use --ast to enable foundry build cache by @​daejunpark in https://github.com/a16z/halmos/pull/289
• fix: add Missing Error Code in parse_build_out Warning by @​pcaversaccio in https://github.com/a16z/halmos/pull/300
• fix bad abi encoding in createBytes4 by @​karmacoma-eth in https://github.com/a16z/halmos/pull/329
• fix: parsing unsat core output variants by @​daejunpark in https://github.com/a16z/halmos/pull/337

New Contributors

• @​pcaversaccio made their first contribution in https://github.com/a16z/halmos/pull/291
• @​EmperorOrokuSaki made their first contribution in https://github.com/a16z/halmos/pull/295
• @​pillip made their first contribution in https://github.com/a16z/halmos/pull/296

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

---

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: 0c2941d

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/[email protected]	eval, filesystem, shell, unsafe	0	870 kB	daejunpark, justin_gerard

🚮 Removed packages: pypi/[email protected])

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 warning	pypi/[email protected]	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 warning	pypi/[email protected]	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 warning	pypi/[email protected]	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	🚫

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore pypi/[email protected]
• @SocketSecurity ignore pypi/[email protected]
• @SocketSecurity ignore pypi/[email protected]

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[ernestognw]

LGTM, we might need to reconsider using Socket, I'm not sure it's giving us useful information