Skip to content
This repository has been archived by the owner on Aug 14, 2024. It is now read-only.

Releases: tjgurwara99/vulnny

v0.0.5

24 Jul 23:46
d312cdf
Compare
Choose a tag to compare

What's Changed

  • Fixing null result in sarif which gets rejected by Code Scanning by @tjgurwara99 in #6

Full Changelog: v0.0.4...v0.0.5

v0.0.4

24 Jul 23:26
50fcbb1
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.0.3...v0.0.4

Vulnny CLI v0.0.3

17 Mar 15:56
99630b0
Compare
Choose a tag to compare

What's Changed

  • Add additional tags in rules plus some end to end tests to ensure no regression occurs when making changes by @tjgurwara99 in #3
  • Fix incorrect help uri from SARIF by @tjgurwara99 in #4

Full Changelog: v0.0.2...v0.0.3

Vulnny CLI v0.0.2

05 Feb 22:31
b6f79fe
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.0.1...v0.0.2

Vulnny CLI v0.0.1

05 Feb 14:39
Compare
Choose a tag to compare

A simple tool to leverage the govulncheck database for finding vulnerabilities in your codebase and report them using the SARIF format.

vulnny is a tool for finding publically known vulnerabilities withing your codebase.
This application is a tool to find the publically known vulnerabilities withing
your codebase using the go tools vulncheck library, the same library used to
power the govulncheck tool.

The -o flag forces vulnny to write the resulting SARIF log to the named
output file, instead of the default behavior of writing the SARIF log
to stdout.

Usage:
  vulnny [-o output] [packages]

Flags:
  -o string
        File to export the SARIF log to