-
Updated
Apr 2, 2022 - JavaScript
dependency-analysis
Here are 163 public repositories matching this topic...
-
Updated
Apr 7, 2022 - TypeScript
-
Updated
Apr 6, 2022 - C++
-
Updated
Jan 11, 2022 - PHP
-
Updated
Dec 27, 2021 - Go
-
Updated
Oct 21, 2021 - Python
-
Updated
Dec 16, 2021 - Python
-
Updated
Mar 6, 2022 - Python
-
Updated
Mar 12, 2022 - C#
Options > Code > Saving
- Ensure that source files end with newline
- Strip trailing horizontal whitespace when saving
-
Updated
Jan 16, 2022 - Python
-
Updated
Jan 2, 2022 - Jupyter Notebook
-
Updated
Jun 2, 2020 - JavaScript
-
Updated
Feb 3, 2022 - Coq
-
Updated
Jan 10, 2022 - JavaScript
Describe the bug
When I try to execute the quickstart guide under windows (via the mingw git bash) the .\jarviz
produces the following error:
java.io.IOException: Cannot run program "mvn": CreateProcess error=2, The system cannot find the file specified
To Reproduce
Just follow the quickstart guide under windows.
- Jarviz version: 0.1.7
- Java version: 1.8.0
**Expec
-
Updated
Apr 7, 2022 - Java
-
Updated
Jun 22, 2021 - Python
-
Updated
Apr 7, 2022 - OCaml
-
Updated
Jun 5, 2019 - Python
-
Updated
Mar 4, 2022 - Python
-
Updated
Apr 6, 2022
In some cases, we assume the name of a library/application is the name of the repository in which the file resides. This works for many projects where you might use a repository per library or application but doesn't work as well for mono-repositories where files may be scattered across subdirectories. One simple way to handle this would be to pass along the file path in addition to the URL to the
-
Updated
Mar 28, 2022 - JavaScript
-
Updated
Apr 8, 2022 - Python
-
Updated
Mar 29, 2022 - C++
Improve this page
Add a description, image, and links to the dependency-analysis topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the dependency-analysis topic, visit your repo's landing page and select "manage topics."
Currently,
NVD_START_YEAR
is configurable with a default value of 2018. The tool should recommend a start year based on the oldest CVE found. If a CVE belonging to the year 2018 is found then the scan should recommend a re-scan with start year of 2017 (Previous year)This can be implemented in the analysis module.