You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Low Risk
CI and packaging-only changes; no runtime consensus or auth logic. Main risk is longer or flakier builds if LLVM install fails on runners.
Overview
Adds LLVM 22 as a build prerequisite for revmc (llvm-sys / LLVM_SYS_221_PREFIX) so CI, release binaries, and Docker can compile the default JIT-enabled world-chain binary.
Introduces .github/scripts/install_llvm_ubuntu.sh (apt.llvm.org via llvm.sh, versioned tool symlinks, permission safeguards) and wires it into rust-ci (cargo-tests, cargo-clippy), releasebuild-binaries, and the Docker base image. Workflow path filters now include the script and .dockerignore; clippy timeout goes from 20 to 30 minutes.
.dockerignore is adjusted so the install script is not excluded from the Docker build context while the rest of .github/ stays ignored.
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 cargo/crossbeam-channel@0.5.16. 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
License policy violation: cargo libgit2-sys under RSA-MD
License: RSA-MD - The applicable license policy does not permit this license (5) (libgit2-sys-0.18.7+1.9.6/libgit2/COPYING)
License: GPL-2.0-or-later - The applicable license policy does not permit this license (5) (libgit2-sys-0.18.7+1.9.6/libgit2/COPYING)
License: GPL-2.0 - The applicable license policy does not permit this license (5) (libgit2-sys-0.18.7+1.9.6/libgit2/COPYING)
License: LGPL-2.1 WITH PCRE2-exception - The applicable license policy does not permit this license (5) (libgit2-sys-0.18.7+1.9.6/libgit2/COPYING)
License: BSD-3-Clause WITH PCRE2-exception - The applicable license policy does not permit this license (5) (libgit2-sys-0.18.7+1.9.6/libgit2/deps/pcre2/LICENCE.md)
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 cargo/libgit2-sys@0.18.7%2B1.9.6. 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
Obfuscated code: cargo openssl is 90.0% likely obfuscated
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: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore cargo/openssl@0.10.81. 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
Obfuscated code: cargo tokio is 90.0% likely obfuscated
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: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore cargo/tokio@1.53.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
License policy violation: cargo webpki-root-certs under CDLA-Permissive-2.0
License: CDLA-Permissive-2.0 - The applicable license policy does not permit this license (5) (webpki-root-certs-1.0.9/Cargo.toml)
License: CDLA-Permissive-2.0 - The applicable license policy does not permit this license (5) (webpki-root-certs-1.0.9/LICENSE)
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 cargo/webpki-root-certs@1.0.9. 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
License policy violation: cargo webpki-roots under CDLA-Permissive-2.0
License: CDLA-Permissive-2.0 - The applicable license policy does not permit this license (5) (webpki-roots-1.0.9/Cargo.toml)
License: CDLA-Permissive-2.0 - The applicable license policy does not permit this license (5) (webpki-roots-1.0.9/LICENSE)
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 cargo/webpki-roots@1.0.9. 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
License policy violation: cargo yoke under Unicode-3.0
License: Unicode-3.0 - The applicable license policy does not permit this license (5) (yoke-0.8.3/LICENSE)
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 cargo/yoke@0.8.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
Obfuscated code: cargo zerocopy is 90.0% likely obfuscated
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: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore cargo/zerocopy@0.8.55. 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
License policy violation: cargo zerofrom under Unicode-3.0
License: Unicode-3.0 - The applicable license policy does not permit this license (5) (zerofrom-0.1.8/LICENSE)
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 cargo/zerofrom@0.1.8. 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.
All three baselines measured on the same runner in the same workflow run. Base and PR are the interpreter at each revision; PR + JIT is the PR revision
built with the revmc JIT backend (--features jit).
JIT vs PR (interpreter → JIT, same revision): 🟡 slower · 🟢 faster. Informational only — never fails the check, since fixtures without heavy bytecode are not expected to gain from JIT.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Low Risk
CI and packaging-only changes; no runtime consensus or auth logic. Main risk is longer or flakier builds if LLVM install fails on runners.
Overview
Adds LLVM 22 as a build prerequisite for revmc (
llvm-sys/LLVM_SYS_221_PREFIX) so CI, release binaries, and Docker can compile the default JIT-enabledworld-chainbinary.Introduces
.github/scripts/install_llvm_ubuntu.sh(apt.llvm.org viallvm.sh, versioned tool symlinks, permission safeguards) and wires it into rust-ci (cargo-tests,cargo-clippy), releasebuild-binaries, and the Docker base image. Workflow path filters now include the script and.dockerignore; clippy timeout goes from 20 to 30 minutes..dockerignore is adjusted so the install script is not excluded from the Docker build context while the rest of
.github/stays ignored.Reviewed by Cursor Bugbot for commit 5f8826e. Configure here.