Inventory of other repositories in opossum-tool

[Hellgartner]

There are currently a lot of repositories in the opossum-tool project

Currently only three of them have an obvious future:

• OpossumUI: Main project
• opossum.lib.py: Plan: use this as main converter library
• opossum.lib.hs: Should be deprecated once opossum.lib.py has reached feature parity

But what about the other libraries available
Check each of them and decide to either

• archive/deprecate
• actively maintain them

[Hellgartner]

Current status of opossum-tool namespace

repository	current state	desired state	Comment
OpossumUI	actively maintained	actively maintained	main repository
opossum-file	actively maintained	actively maintained
opossum.lib.hs	open to public	private archive	predecessor of opossum-file, to be archived once feature parity has been reached
proximity-matcher-crystal	private	private archive ???	result of a hackaton 2023
aioc	last commit 4 years ago	???	aioc = all in one container, see below for details
TERN-to-opossum-converter	last commit 4 years ago, private	private archive	archive as soon as TERN is part of opossum-file
examples	public	private archived ??	examples generated with aioc --> depends on aioc future
old-opossumUI	private archive	private archive
opossum-sandbox	private	private archive ??	looks like a poc for aioc
SCANOSS-to-opossum-converter	private archive	private archive
FossID-to-opossum-converter	private	private archive	integrate into opossum-file
Bootstrap-Opossum	private	private archive	looks like another aoic predecessor
opossumcs	private archive	private archive
hhch	private archive	private archive

Project details

aioc

• Container based pipeline to scan a folder using 4 dependency scanners
• Works on opossum.lib.hs
• Still produces the outdated opossum format
• State:
  • demonstrator / not production ready
  • Last commit 4 years ago
• Uses opossum.lib.hs and oss-review-toolkit as git submodules

Options

Abandon

• archive

Revive

• move to opossum-file (and make it produce proper opossum files)
  • requires feature parity first (especially readable formats)
• Update docker pipeline to te up to date again
  • Uses hardcoded versions of subprojects
• Can this be bundled?
• Pro: Great tool for scanning any project from multiple directions
• Con: Effort

[Hellgartner]

Action items

• Archive haskell tool
• Create issue in AIOC
• Check whether exiftool works on recursive and create story if requested
• Issues for merging and splitting