Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

analyse and fix dependencies findings #1697

Open
neoheat opened this issue Mar 6, 2024 · 2 comments
Open

analyse and fix dependencies findings #1697

neoheat opened this issue Mar 6, 2024 · 2 comments

Comments

@neoheat
Copy link
Collaborator

neoheat commented Mar 6, 2024

According to analysis of @SeduroDotCom

  • check findings of dependencies check
  • fix and update
@neoheat
Copy link
Collaborator Author

neoheat commented Apr 24, 2024

to be specified in more detail, which project etc.

@SeduroDotCom
Copy link
Contributor

  1. For more details concerning legacy-vulns (mr/legacy-vuln) see mail from 26.2 / 6.3
  2. @nimaai mr/legacy-vuln contains solutions/fixes to get rid of all critical-issues

Maybe next steps

  1. Setup analyzing-tools, ruby (brakeman) & clojure (nvd-clojure) in each leihs-project to get an overview
    a. legacy .. see mail
    b. procure .. see mail
    c. mail .. todo
    d. borrow .. todo
    e. my .. todo
    f. admin .. todo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Technical
Development

No branches or pull requests

2 participants