Source: https://seerepo.com/r/epi052/feroxbuster
Markdown source: https://seerepo.com/r/epi052/feroxbuster.md
Description: epi052/feroxbuster is a Rust repo with 33,204 lines written. feroxbuster is built with Tokio.

# What's inside epi052/feroxbuster

epi052/feroxbuster is a Rust repo with 33,204 lines written. feroxbuster is built with Tokio.

Its description on GitHub: “A fast, simple, recursive content discovery tool written in Rust.”

Rust · MIT · 8,183 stars · GitHub: https://github.com/epi052/feroxbuster

Read on November 17, 2026, at commit f89b6c6.

## More on this repo

- [What is feroxbuster built with?](https://seerepo.com/r/epi052/feroxbuster/built): feroxbuster is built with Tokio.
- [How much of feroxbuster did AI write?](https://seerepo.com/r/epi052/feroxbuster/ai): No AI tool signed any of the 1,604 commits of feroxbuster.

## In figures

- 33,204 lines written: The ones people and agents wrote: product, tests, schemas and tooling. Generated code doesn’t count.
- 70 product files: The product’s own files. Test files are counted apart.
- 24 test files: The files that test the code.
- 7 technologies: Each service with the file and line that prove it.

SeeRepo read the facts in its code and kept none of it. AI only helps sort its packages and folders by their names, and never sees its code.

## Frequently asked questions

### What is epi052/feroxbuster?

epi052/feroxbuster is a Rust repo with 33,204 lines written. Its description on GitHub: “A fast, simple, recursive content discovery tool written in Rust.”

The proof: [its page on GitHub](https://github.com/epi052/feroxbuster)

### What is feroxbuster built with?

feroxbuster is built with Tokio.

The proof: [each service with its file and line](https://seerepo.com/r/epi052/feroxbuster/built)

### What license does feroxbuster have?

feroxbuster is released under the MIT license.

The proof: [its page on GitHub](https://github.com/epi052/feroxbuster)

### How many stars does feroxbuster have on GitHub?

feroxbuster had 8,183 stars on GitHub on November 17, 2026.

The proof: [its page on GitHub](https://github.com/epi052/feroxbuster)

## Add this badge to your README

It links to this page and updates itself each time SeeRepo reads the repo.

```markdown
[![epi052/feroxbuster on SeeRepo](https://seerepo.com/badge/epi052/feroxbuster.svg)](https://seerepo.com/r/epi052/feroxbuster?de=insignia)
```

## What is your repo built with?

Any public repo, with no account: https://seerepo.com/r/owner/repo/built, with the owner and name it has on GitHub.
