Add allowed_duplicates to the file generator script
What the developer wrote
Authored by Shing Him Ng
Add allowed_duplicates to the file generator script
What changed, and why it matters
This commit changes only a fuzz-testing helper shell script. It adds a configuration entry telling an internal lint tool (rbmt) that the crate 'hex-conservative' is allowed to appear as a duplicate dependency in the fuzz workspace. There is no change to production code, no cryptographic logic, no network handling, and no user-facing behavior. It is not a security fix and does not introduce a security issue.
No security action needed. Review as a normal build-script maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch appends a [package.metadata.rbmt.lint] section with allowed_duplicates = [“hex-conservative”] to the Cargo.toml generated by fuzz/generate-files.sh. This is a build/lint configuration relaxation for the fuzz workspace only, permitting the hex-conservative crate to be present multiple times in the dependency graph. The change is limited to fuzz infrastructure and has no runtime or library security implications.
Changed components
fuzz/generate-files.shInspect captured patch +5 / −0
diff --git a/fuzz/generate-files.sh b/fuzz/generate-files.sh
index ec03349a..6d34a6fe 100755
--- a/fuzz/generate-files.sh
+++ b/fuzz/generate-files.sh
@@ -38,6 +38,11 @@ unexpected_cfgs = { level = "deny", check-cfg = ['cfg(fuzzing)'] }
[lints.clippy]
redundant_clone = "warn"
use_self = "warn"
+
+[package.metadata.rbmt.lint]
+allowed_duplicates = [
+ "hex-conservative",
+]
EOF
for targetFile in $(listTargetFiles); do
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.