You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updated sarif library to v3 from v2. Still outputting SARIF 2.1 as that
is what github supports.
I also changed how sarif_test snapshots are generated in the first
commit to make it easier to see the diff, so when reviewing, please see
the differences between the first commit and the last one for the
snapshots, don't look at the full thing.
~~Currently it seems like there's an issue with ruleIndex being
populated with -1 rather that the actual rule index, not sure why yet,
I'll post an issue on the libraries repo.~~
Solved! Updated to v3.2.0 which resolved the above issue.
Copy file name to clipboardExpand all lines: docs/guided-remediation.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -738,7 +738,6 @@ The following flag may be used to limit the patches allowed for your dependencie
738
738
-`--upgrade-config=<[package-name:]level>` Sets the maximum upgrade level allowed for a package. Can be repeated for multiple packages.
739
739
740
740
`level` is the SemVer component to allow updates to, can be one of `major`, `minor`, `patch`, or `none`. e.g. If a package was at version `1.2.3`
741
-
742
741
-`major` allows for updates to any version `>=1.2.3`
743
742
-`minor` allows for updates `>=1.2.3, <2.0.0`
744
743
-`patch` allows for updates `>=1.2.3, <1.3.0`
@@ -749,7 +748,6 @@ The following flag may be used to limit the patches allowed for your dependencie
749
748
Default behaviour is `--upgrade-config=major`.
750
749
751
750
Example usage:
752
-
753
751
-`--upgrade-config=minor` - disallow any patches that would bump a major version of any package.
754
752
-`--upgrade-config=foo:minor` - disallow any patches that bumps package `foo` by a major version. Other packages may receive major version-updating patches.
755
753
-`--upgrade-config=none --upgrade-config=foo:patch` - only allow patches to package `foo`, and only allow changes to `foo`'s SemVer patch level.
Copy file name to clipboardExpand all lines: docs/scan-image.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,15 +39,13 @@ You can scan container images using two primary methods:
39
39
```bash
40
40
osv-scanner scan image image-name:tag
41
41
```
42
-
43
42
-**How it works:** OSV-Scanner uses `docker save` to export the image to a temporary archive, which is then analyzed. No container code is executed during the scan.
44
43
45
44
2.**Scan from Exported Image Archive:** If you have already exported your container image as a Docker archive (`.tar` file), you can scan it directly using the `--archive` flag. This method does not require Docker to be installed.
0 commit comments