Ayan Sinha Mahapatra
Ayan Sinha Mahapatra
@pombredanne @JonoYang This is ready to review!
@pombredanne All green!
@pombredanne should this be closed as this is merged?
https://github.com/nexB/scancode-toolkit-reference-scans has been added to store scancode-toolkit reference scans and documentation on output version changes with diffs. Repository: https://scancode-toolkit-reference-scans.readthedocs.io/en/latest/ This needs to be added to scancode-toolkit documentation.
So we have file level license field name changes [here in this commit](https://github.com/nexB/scancode-toolkit/pull/2961/commits/4fc7d24ada087c73c58bf228930958c777791532) and all the package level field name changes are [here in this commit](https://github.com/nexB/scancode-toolkit/pull/2961/commits/af4dec73bf1129fdbe76b77b83e44c8fd747a5e9). But the later one...
I was testing out the very basic gibberish detector at https://github.com/rrenaud/Gibberish-Detector, which https://github.com/domanchi/gibberish-detector (mentioned above is based on), as it is much easier to integrate. I used our scancode license...
I still think we need better performance to integrate, i was looking into the other implementation which is a library. There are some additional steps there so I'll try that...
@pombredanne I have a couple of possible cases here which could be clues, as opposed to detections. what do you think? i.e. they will have is_clue as `True` in their...
This is https://github.com/nexB/license-expression/issues/67
Thanks for the report, I could reproduce from this JSON file you attached, and looking into this.