Skip to content

Collection of existing examples for Dependency Analyzer Source #97

@mkurzman

Description

@mkurzman

| Comments | Analysis and dependency resolution is highly language specific. Thus a language specific implementation might be required<br>Discussion: Would it make sense to declare a task or responsibility to stop CI/CD in sit of violation? |

[Meta Level]
This issue is used as example for potential collaboration in our regular meeting.
Steps:

  • go to the file
  • go to the code
  • go to the line
  • click on the 3 dots and
  • click "Reference in new issue"
  • add your issue comment

[Content Level]
I would appreciate to have a collection of examples in the description. That would help to get familiar with the capabilities.
In this special case I would list at least

  • the OSS Review Toolkit Analyzer (https://github.com/oss-review-toolkit/ort#analyzer)
    Hint: also with other tools, the naming of the overall tool would potentially be too vague so that the detailed sub-feature/component would need to be referred to, to have the correct capability mapping. A naming convention like [Overall Tool Name]/[Sub Component/Function] may be helpful

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions