Does cdxgen allow to specify the ecosystem and/or the definition file of the packages?

[emil-wire]

In a repository with multiple ecosystems like a requirements.txt, a package.json and a Dockerfile, can one instruct cdxgen to specify which ecosystem the package belongs to or where it found the package in question? Especially in mono repos, that can potentially host a multitude of Dockerfiles, it would save a lot of time to be able to pinpoint where the dependency was defined. Such as certifi 1.2.3. came from componentA/requirements.txt and certifi 2.3.4 came from randomTool/requirements.txt

[prabhu]

You can -t python,-t js etc. The resulting bom file would always have a property to identify the source file

[emil-wire]

I assume when one uses -t universal or -r this wouldn't happen?
What happens if I specify all available -t $supportedEcosystems but the ecosystem isn't present during the generation?

[emil-wire]

for anyone else wondering about this, there is the --evidence true flag or the scan profile research that also provides evidence.