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
Copy file name to clipboardExpand all lines: docs/docs/coverage/language/dotnet.md
+3-6
Original file line number
Diff line number
Diff line change
@@ -21,15 +21,12 @@ The following table provides an outline of the features Trivy offers.
21
21
## *.deps.json
22
22
Trivy parses `*.deps.json` files. Trivy currently excludes dev dependencies from the report.
23
23
24
+
!!! note
25
+
Trivy only includes runtime dependencies in the report.
26
+
24
27
## packages.config
25
28
Trivy only finds dependency names and versions from `packages.config` files. To build dependency graph, it is better to use `packages.lock.json` files.
26
29
27
-
### libraries built into .NET Core
28
-
[libraries section][net-core-libraries] of `*deps.json` file may contain dependencies that included to `.NET Core` (dependencies with empty `runtime`, `runtimeTarget` and `native` fields in [target][net-core-target] section).
29
-
These dependencies are not needed by the runtime, and the `dotnet build` command doesn't create `*.dll` files for them.
30
-
31
-
Trivy marks these dependencies as the development dependencies and skip them by default. If you need to show them, use the `--include-dev-deps` flag.
32
-
33
30
## *Packages.props
34
31
Trivy parses `*Packages.props` files. Both legacy `Packages.props` and modern `Directory.Packages.props` are supported.
0 commit comments