Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
128 changes: 115 additions & 13 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ signal-hook = "0.4"
tokio = { version = "1", default-features = false, features = ["macros", "rt", "time"] }

[dev-dependencies]
aes-gcm = "0.10"
aes-gcm = "0.11"
Comment thread
kodus-27b[bot] marked this conversation as resolved.
Resolved
Comment thread
kodus-27b[bot] marked this conversation as resolved.
Resolved
Comment thread
kodus-27b[bot] marked this conversation as resolved.
Resolved
Comment thread
kodus-27b[bot] marked this conversation as resolved.
Resolved

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kody code-review Kody Rules high

Unresolvable dependency requirement in Cargo.toml: the dev-dependency aes-gcm is bumped from 0.10 to 0.11, but 0.11 has mostly been published as pre-release (rc) versions, and Cargo's plain 0.11 requirement does not match those. If no stable 0.11.x release exists, cargo test fails to resolve aes-gcm; if one does resolve, the 0.x minor bump can change the cryptographic APIs and pull in new transitive crates such as aead and cipher without any audit evidence. Fix: pin a confirmed stable 0.11.x release explicitly, commit the updated Cargo.lock, and attach cargo audit (or OSV/SCA) output to the PR description.

Kody rule violation: Validate new/updated dependencies for CVEs and supply-chain risk

Prompt for LLM

File Cargo.toml:

Line 44:

Unresolvable dependency requirement in Cargo.toml: the dev-dependency `aes-gcm` is bumped from 0.10 to 0.11, but 0.11 has mostly been published as pre-release (rc) versions, and Cargo's plain `0.11` requirement does not match those. If no stable 0.11.x release exists, `cargo test` fails to resolve `aes-gcm`; if one does resolve, the 0.x minor bump can change the cryptographic APIs and pull in new transitive crates such as `aead` and `cipher` without any audit evidence. Fix: pin a confirmed stable 0.11.x release explicitly, commit the updated Cargo.lock, and attach `cargo audit` (or OSV/SCA) output to the PR description.

Talk to Kody by mentioning @kody

Was this suggestion helpful? React with πŸ‘ or πŸ‘Ž to help Kody learn from this interaction.

​

​

async-trait = "0.1"
hkdf = "0.12"
rustix = { version = "1", features = ["pty"] }
Expand Down
Loading