|
20 | 20 | displaying the vulnerability report. |
21 | 21 | <p> |
22 | 22 | <b>IMPORTANT:</b> |
23 | | - <br>Currently, Dependency Analytics only supports projects that use Maven (<code>mvn</code>), and Node |
24 | | - (<code>npm</code>, <code>pnpm</code> or <code>yarn</code>), Golang (<code>go mod</code>) and Python (<code>pip</code>) ecosystems, and base images in |
25 | | - <code>Dockerfile</code>. |
26 | | - <br>In future releases, Red Hat plans to support other programming languages. |
| 23 | + <br>Dependency Analytics supports multiple package managers: |
| 24 | + <li>Maven (mvn)</li> |
| 25 | + <li>NPM (npm)</li> |
| 26 | + <li>PNPM (pnpm)</li> |
| 27 | + <li>Yarn Berry and Classic (yarn)</li> |
| 28 | + <li>Gradle Kotlin and Groovy (gradle)</li> |
| 29 | + <li>Golang (go mod)</li> |
| 30 | + <li>Python (pip) ecosystems, and base images in Dockerfile.</li> |
| 31 | + <br>In future releases, Red Hat plans to support other package managers.</br> |
27 | 32 | <p> |
28 | 33 |
|
29 | 34 | <h2>Quick Start</h2> |
|
34 | 39 | IDE's <code>PATH</code> environment. |
35 | 40 | </li> |
36 | 41 | <li>For Node projects, analyzing a <code>package.json</code> file, you must have one of the corresponding package manager <code>npm</code>, <code>pnpm</code> or <code>yarn</code> and |
37 | | - <code>node</code> binaries in your IDE's <code>PATH</code> environment. |
| 42 | + <code>node</code> binaries in your IDE's <code>PATH</code> environment. It also requires a corresponding lock file to be present in order to analyze package.json files. |
38 | 43 | </li> |
39 | 44 | <li>For Golang projects, analyzing a <code>go.mod</code> file, you must have the <code>go</code> binary in your |
40 | 45 | IDE's <code>PATH</code> environment. Furthermore, Golang projects can only be analyzed with IntelliJ Ultimate Edition. |
41 | 46 | </li> |
42 | 47 | <li>For Python projects, analyzing a <code>requirements.txt</code> file, you must have the <code>python3</code> and |
43 | 48 | <code>pip3</code> binaries in your IDE's <code>PATH</code> environment. |
44 | 49 | </li> |
| 50 | + <li> |
| 51 | + For Gradle projects, analyzing a <code>build.gradle</code> file or <code>build.gradle.kts</code> file, you must have the <code>gradle</code> binary in your system's <code>PATH</code> environment. |
| 52 | + </li> |
45 | 53 | <li>For base images, analyzing a <code>Dockerfile</code>, you must have the <code><a |
46 | 54 | href="https://github.com/anchore/syft?tab=readme-ov-file#installation" rel="noopener noreferrer" |
47 | 55 | target="_blank">syft</a></code> and |
|
114 | 122 | executable. |
115 | 123 | <br>If the paths are not provided, your IDE's <code>PATH</code> environment will be used to locate the |
116 | 124 | executables. |
| 125 | + <br>It also requires a corresponding lock file to be present in order to analyze package.json files. |
117 | 126 | </li> |
118 | 127 | <li> |
119 | 128 | <b>Golang</b>: |
|
142 | 151 | dynamically instead. This feature cannot be enabled when <code>Strictly match package version</code> is |
143 | 152 | selected. |
144 | 153 | </li> |
| 154 | + <li> |
| 155 | + <b>Gradle</b>: |
| 156 | + <br>Set the full path of the Gradle executable, which allows Exhort to locate and run the <code>gradle</code> |
| 157 | + command to resolve dependencies for Gradle projects. |
| 158 | + <br>By not setting a path to the gradle binary, IntelliJ IDEA uses its default path environment to locate |
| 159 | + the file. |
| 160 | + </li> |
145 | 161 | <li> |
146 | 162 | <b>Image</b>: |
147 | 163 | <br>Set the full path of the Syft executable, which allows Exhort to locate and execute the <code>syft</code> |
|
376 | 392 | <change-notes><![CDATA[ |
377 | 393 | <p><b>1.1.0</b></p> |
378 | 394 | <p>Added support for Gradle manifest files.</p> |
| 395 | + <p>Added support for Yarn.</p> |
| 396 | + <p>Added support for PNPM.</p> |
| 397 | + <p>Added support for Proxy setting(Static Proxy Configuration).</p> |
| 398 | + <p>Enable using the Maven Wrapper.</p> |
| 399 | + <p>No restart needed after installation.</p> |
| 400 | + <p>Require a lock file to be present in order to analyze package.json files.</p> |
379 | 401 | <p><b>1.0.0</b></p> |
380 | 402 | <p>Added support for base image vulnerability scanning in Dockerfiles.</p> |
381 | 403 | <p>Bumped Telemetry plugin to 1.1.0.</p> |
|
0 commit comments