fix(security): close remaining scan alerts - #69
Merged
Conversation
Signed-off-by: StringKE <stringke.me@gmail.com>
StringKe
added a commit
that referenced
this pull request
Aug 13, 2026
Bump the repository release version to 0.0.3 and generate release notes for the security hardening merged in PR #69. Signed-off-by: StringKE <stringke.me@gmail.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
contents: writeonly to the release jobevent-listenerin the Linux SDK lockfile from5.4.1to5.4.2concurrent-queueandcrossbeam-utilslock entriesSecurity context
TokenPermissionsIDalert feat(site): launch localized product landing #43RUSTSEC-2026-0221from the Linux SDK dependency graphimage-sizefindings in Scorecard alert chore(deps): Bump the nuget group with 4 updates #3 are already remediated bypatches/image-size@1.2.1.patch; Scorecard matches registry versions and cannot identify the backportMaintainedIDalert chore(deps): bump the cargo group across 2 directories with 15 updates #5 is an immutable repository-age signal and will age out after 90 daysVerification
cargo audit --file sdk/linux/Cargo.lock: 0 vulnerabilities, 0 warningspnpm audit --prod --audit-level high: no known vulnerabilitiespnpm run test:release-contracts: 60 tests PASSpnpm run check: PASSpnpm test: PASSgit diff --check: PASS