ThreatMapper VS fst

Though the Reddit-Mod war has delivered another excellent find. well several actually, but the one I'm posting now is called "Threat Mapper". Its a security scanner, will a fantastic UI, and works across most infrastructure... including VMs, Containers and the main Cloud Providers..

https://github.com/deepfence/ThreatMapper

If you like Wiz.io but don't have a million dollars or so lying around, I'm finding the community edition of Deepfence (https://deepfence.io/) pretty good.

Magpie https://github.com/openraven/magpie ThreatMapper https://github.com/deepfence/ThreatMapper Cloudquery https://github.com/cloudquery/cloudquery

Company: https://deepfence.io

And deepfence.imo for vurnalbility scans https://github.com/deepfence/ThreatMapper

ThreatMapper is an option for your team member, particularly if you're looking to scan Kubernetes or Fargate environments as the installation is very easy. It's a little more complex for hosts (you need to install a docker runtime on each to run the sensor locally), but should be worth any additional trouble. The GUI gives you a map of workloads, traffic flows, vulnerabilities found on each workload and host, and which are highest risk.

Full disclosure - I work for an open source project called ThreatMapper that performs run-time vulnerability scanning and anything you say might be used to make the project better - thank you!

I'd point you towards BurntSushi's fst crate: https://github.com/BurntSushi/fst

The fst crate effectively relies on mmap for it to work right. The folks here suggesting you just use the heap might be right, but only if using the heap is actually plausible. If your dictionary is GBs big (an FST might be bigger than available memory), then copying it the heap first would be disastrous.

You'll love what we're working on if you're interested in the implementation of:- Tantivy- Meilisearch- Finite State Transducers

Here's an example of longest prefix matching using a FST which I based my approach on: https://github.com/BurntSushi/fst/pull/104/files

Finite State Transducers

As a result, I have a plan to implement a desktop version from then and I finished today with a beta version. The desktop is based on tauri, and the dictionary index algorithm is FST (it is an awesome index algorithm).

WordBueno’s data is currently derived from Wiktionary. The backend is using Rust’s warp with fst for indexing.

No you don't. I've written multiple programs that load things instantly off the file system via memory maps. See the fst crate[1], for example, which is designed to work with memory maps.

Rust "works badly with memory mapped files" doesn't mean, "Rust can't use memory mapped files." It means, "it is difficult to reconcile Rust's safety story with memory maps." ripgrep for example uses memory maps because they are faster sometimes, and its safety contract[2] is a bit strained. But it works.

[1] - https://github.com/BurntSushi/fst/

[2] - https://docs.rs/grep-searcher/0.1.7/grep_searcher/struct.Mma...