GIT-PKGS(1)

πŸ“¦
version 0.21.0 Β· 2 versions
, in nixpkgs unstable

πŸ’… GIT-PKGS(1) β€” the Git Pkgs Manual, bestie edition

okay so picture this: it's the git-pkgs manual, but it's got main character energy now. Everything's still here, no cap β€” same flags, same defaults, same everything. Let's go 🫢


✨ NAME ✨

git-pkgs-vulns-log β€” literally the command that shows you which commits changed a vulnerability's state. That's it, that's the vibe check. πŸ’–


🌸 SYNOPSIS 🌸

git-pkgs vulns log [flags]

πŸ¦‹ DESCRIPTION πŸ¦‹

So this one lists out the commits that introduced or fixed vulnerabilities β€” like a little timeline of how your vulns have been living their lives over time. Glow-ups, glow-downs, all of it. It's giving history channel but make it security. πŸ”₯


πŸŽ€ OPTIONS πŸŽ€

okay so here's the whole flag menu, do not skip, I'm not skipping:

  • --author="" β€” filter by author name or email. You know, so you can be like "what did they do" πŸ™ˆ
  • -b, --branch="" β€” the branch to query. Default is the first tracked branch, so it's already picking for you, slay.
  • -e, --ecosystem="" β€” filter by ecosystem. Narrow it down, diva.
  • --fixed[=false] β€” only show commits that fixed vulnerabilities. i.e. the heroes. πŸ‘‘
  • -f, --format="text" β€” output format. Your options are text and json. Pick your fighter.
  • -h, --help[=false] β€” help for log. Bestie it's right there ✨
  • --introduced[=false] β€” only show commits that introduced vulnerabilities. i.e. the villains. πŸ’€
  • --limit=20 β€” max commits to check. Default is 20, so it's not gonna scroll forever, thank god.
  • -s, --severity="" β€” minimum severity. Your choices: critical, high, medium, low. Ranked, obviously.
  • --since="" β€” only commits after this date. Format is YYYY-MM-DD, keep it exact.
  • --until="" β€” only commits before this date. Also YYYY-MM-DD. Bookends, we love her. 🌈

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

these come from the parent command, so they're just living rent-free in here:

  • --color="auto" β€” when to colorize output. Options: auto, always, never. Default auto, because she's decisive-but-chill.
  • --include-submodules[=false] β€” include git submodules when scanning for manifests. Lowkey important if you're That Person with submodules everywhere.
  • -p, --pager[=false] β€” use pager for output.
  • -q, --quiet[=false] β€” suppress non-essential output. For when you want peace and quiet fr fr.

⭐ SEE ALSO ⭐


🌷 HISTORY 🌷

  • 28-Oct-2026 β€” auto generated by spf13/cobra. Not me getting a robot to write my lore 😭

aaaaand scene. that was git-pkgs from the Git Pkgs Manual, dated Oct 2026 β€” mwah, go touch some manifests πŸ’…βœ¨πŸ“

πŸ“¦ where this page comes from