Brad Larsen

@tosiara thanks for the detailed report! Indeed, Nosey Parker's build process is more brittle than those of pure Rust projects. In particular, the [Vectorscan](https://github.com/VectorCamp/vectorscan) dependency is a large C++ codebase...

See also https://github.com/praetorian-inc/noseyparker/issues/100#issuecomment-1854278243: it may be possible to cross-compile using the [`cross`](https://crates.io/crates/cross) tool and/or the `RUSTFLAGS="-C target-features=+crt-static"` flag, which [statically links the C runtime](https://doc.rust-lang.org/reference/linkage.html#static-and-dynamic-c-runtimes).

@tosiara FYI, I was able to get cross-compilation working now on a M3 mac. I ran in Docker on macOS in the `rust:latest`, which includes `cargo 1.80.1 (376290515 2024-07-16)`. I...

Hi @Coruscant11. This is a good use case and a feature that would be nice to have. One challenge with implementing this in Nosey Parker is that Git repos are...

Another related change to this that I'd like to make in Nosey Parker is to keep track of which inputs have already been scanned, and avoid rescanning them if possible....

See also: https://github.com/praetorian-inc/noseyparker/issues/30

> I had a question, in some repositories, the scanner will found the same amount of distinct match at every run but not the same amount of total matches. Do...

@Coruscant11 That is surprising. If you run `noseyparker summarize --datastore np.vegas` multiple times, does it always report the same numbers, or do those change from run to run?

Yeah that doesn't look right! Thanks for reporting that. A separate issue would be perfect.

@Coruscant11 I created a new issue for the strange behavior your see: #32