nyx/tests/fixtures/async_rust
Eli Peter a438886217
Python fp and docs updtes (#58)
* refactor: Update comments for clarity and add expectations.json files for performance metrics

* feat: Implement FP guard for JS/TS local-collection receivers to suppress missing ownership checks

* feat: Enhance Rust parameter handling to classify local collections and prevent false ownership checks

* refactor: Simplify code formatting for better readability in multiple files

* refactor: Improve UTF-8 sequence length handling and enhance clarity in loop iteration

* feat: Update Java and Python patterns to include new security rules

* refactor: Improve comment clarity and consistency across multiple Rust files

* refactor: Simplify code formatting for improved readability in integration tests and module files

* refactor: Improve comment formatting and enhance clarity in assertions across multiple files
2026-04-29 19:53:34 -04:00
..
expectations.json Release/0.5.0 (#35) 2026-04-25 17:59:11 -04:00
main.rs Python fp and docs updtes (#58) 2026-04-29 19:53:34 -04:00
README.md Release/0.5.0 (#35) 2026-04-25 17:59:11 -04:00

async_rust — Rust async flow regression

Flow

fetch_and_exec reads CMD from the environment and passes it to tokio::process::Command::new("sh").arg("-c").arg(&cmd). The intended finding is taint-unsanitised-flow from the env source to the Tokio process-spawn sink.

Note on docs/language-maturity.md

The maturity doc previously listed Tokio process variants as a known gap for Rust. The engine now surfaces this flow, so the fixture is codified with required_findings and will regression-guard that coverage going forward. If the maturity doc still claims this gap, it should be updated alongside any future refactor that reopens it.