Skip to content
#

software-composition-analysis

Here are 16 public repositories matching this topic...

pombredanne
pombredanne commented Sep 5, 2020

There are about ~240 URLs and licenses listed at https://directory.fsf.org/wiki?title=Category:License
We should:

  1. ensure that we can detect all of them
  2. ensure that we can detect their URL
    We should also add as an "other_urls" ech URL to the corresponding license YAML

fsf-license-urls.txt

stevespringett
stevespringett commented Nov 18, 2020

The current swagger definition is autogenerated. The automatically generated definitions rely on reflection and annotations to create the documentation. The reflection capabilities are poor at best and lead to missing API parameters. Annotations can help in some cases, but the only fix for Swagger is to create individual POJOs for every possible request. This will lead to unnecessary large number

pmckeown
pmckeown commented Oct 8, 2020

Current output from the findings goal looks like the example below. It would be useful to have the Name of the issue in the output too.

Current:

[INFO] MEDIUM: org.apache.struts:struts-core:1.3.5
[INFO] 
[INFO] ** DISPUTED ** The DebuggingInterceptor component in Apache Struts befor
[INFO] e 2.3.1.1, when developer mode is used, allows remote attackers to execu
[INFO] te arbitrary c

Improve this page

Add a description, image, and links to the software-composition-analysis topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the software-composition-analysis topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.