clearlydefined / clearlydefined/service
Accept SPDX files as curation
- Dominant language
- TypeScript
- Stars
- 51
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
There are many out there – including me – who are auditing/scanning packages with tools such as FOSSology and ScanCode and then storing their conclusions typically in an [SPDX file format (RDF, tag:value, YAML or JSON flavour)](https://spdx.github.io/spdx-spec/1-rationale/#17-format-requirements), as a common standard (pending ISO standard).
Some of us would be happy to contribute those conclusions to a common data-set, such as ClearlyDefined, but the current workflow is not accommodating to an SPDX file use-case.
If I spend hours auditing a complex package that includes parts that need human (perhaps even expert) interpretation – and those packages are the ones that typically benefit from curation – , it is hard for me to justify spending much additional time to translate the data of my findings from a standard format to a custom one, just so I can upload it.
Now if ClearlyDefined were to accept SPDX files as input that you can simply upload as a curation, that would make it immensely more easy to contribute to.
—
P.S. I apologise, I honestly thought I had already submitted this issue a long time ago.
Contributor guide
Assessment
This issue has not been assessed yet.