FSRT compatible with custom ui?

Hi Team,

I tried to run Forge Security Requirement Tester on my project but it gave me the error below:

thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', crates/forge_analyzer/src/engine.rs:107:13
stack backtrace:
   0: rust_begin_unwind
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panicking.rs:575:5
   1: core::panicking::panic_fmt
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/panicking.rs:65:14
   2: core::panicking::panic
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/panicking.rs:115:5
   3: forge_analyzer::engine::Machine::run
   4: fsrt::ForgeProject::verify_funs::{{closure}}
             at /home/nagyi/dev/FSRT/crates/fsrt/src/main.rs:95:37
   5: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/ops/function.rs:309:13
   6: core::option::Option<T>::map
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/option.rs:925:29
   7: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::next
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/iter/adapters/map.rs:103:9
   8: fsrt::scan_directory
             at /home/nagyi/dev/FSRT/crates/fsrt/src/main.rs:221:34
   9: fsrt::main
             at /home/nagyi/dev/FSRT/crates/fsrt/src/main.rs:241:9
  10: core::ops::function::FnOnce::call_once
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/ops/function.rs:251:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Is FSRT able to scan projects with custom ui? Is there any roadmap and documentation about this product?

Hi, you can file an issue with FSRT here: Sign in to GitHub · GitHub. FSRT doesn’t scan any custom UI code at the moment, however, it should still support projects that use custom UI modules.

Also, the you might want to pull the latest changes, since the most recent batch of commits fixed a similar issue. We’re planning on properly versioning fsrt, but for now you unfortunately have to just pull from main.