VULS(1)

πŸ“¦ version 0.6.1, in ubuntu jammy, ubuntu noble, ubuntu questing

πŸ’– VULS(1) β€” the user manual, but make it cute πŸ’–

okay bestie, pull up a chair, because we're about to get SO cozy with vuls β€” a Vulnerability scanner for Linux/FreeBSD. yes, that's the whole vibe. it finds vulns. it's giving security girlboss. πŸ¦‹


✨ NAME ✨

vuls β€” Vulnerability scanner for Linux/FreeBSD πŸ”₯


🌸 SYNOPSIS 🌸

vuls <flags> <subcommand> <subcommand args>

that's it. that's the whole shape of it. flags first, then the subcommand, then whatever that subcommand is hungry for. order matters, bestie, don't come for me πŸ’…


πŸŽ€ DESCRIPTION πŸŽ€

πŸ’« Subcommands:

  • commands β€” lists out every single command name like it's reading the group chat roster πŸ“‹
  • flags β€” spills the tea on all the known top-level flags 🚩
  • help β€” describes the subcommands and their syntax, aka the friend who actually explains the plan 🫢

πŸ¦‹ Subcommands for configtest:

  • configtest β€” test your configuration. vibe check your config file before it embarrasses you in public ✨

🌈 Subcommands for discover:

  • discover β€” host discovery in the CIDR. it goes and finds who's in the neighborhood 🏘️

πŸ’œ Subcommands for history:

  • history β€” list history of scanning. receipts. all of them. πŸ“œ

⭐ Subcommands for report:

  • report β€” reporting. making it look pretty so people actually read it πŸ“Š

πŸ‘‘ Subcommands for scan:

  • scan β€” scan vulnerabilities. the main character moment. the whole point. πŸ’₯

🧚 Subcommands for tui:

  • tui β€” run Tui view to analyze vulnerabilities 🌈 a whole little terminal world for staring at your vulns in style.
psst β€” use "vuls flags" for a list of top-level flags πŸ‘€

πŸ› REPORTING BUGS πŸ›

found a bug? tell the people! report it to:

https://github.com/future-architect/vuls/issues

they wanna hear it, fr fr πŸ™ˆ


Copyright 2016 Future Architect, Inc. Japan. πŸ‘‘


and that's the whole page, bestie! this is vuls 0.4.2 from April 2018, living its life as page VULS(1) in the User manual. now go scan something and slay πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from