4 ms·
Good luck checking every code line for license violations
by croes 5y ago
Good luck checking every code line for license violations
- dr_kiszonka 5y agoThere will be a VSCode extension for that.
- croes 5y agoSame trust issue
- TheDong 5y agoIt's impossible to automate checking for code license violations. If you and I write the exact same 10 lines of code, we both have independent and valid copyrights to it. Unlike patents, independent derivation of the same code _is_ a defense for copyright. If I write 10 lines of code, publish it as GPL (but don't sign a CLA / am not assigning it to an employer), and then re-use it in an MIT codebase, I can do that because I retained copyright, and as the copyright holder I can offer the code under multiple incompatible licenses. There's no way for a machine to detect independent derivation vs copying, no way for the machine to know who the original copyright holder was in all cases, and whether I have permission from them to use it under another license (i.e. if I email the copyright holder and they say 'yeah, sure, use it under non-gpl', it suddenly becomes legal again)... It's not a problem computers can solve 100% correctly.
- dr_kiszonka 5y agoI should have added /s to highlight that I was being sarcastic. Sorry.
- duckmysick 5y agoSaaS idea: code linter, but for licenses.
- adrianN 5y agoExtend Fossology: https://www.fossology.org/ https://www.fossology.org/
- SahAssar 5y agoThat's one of blackduck's offerings: https://www.synopsys.com/software-integrity/open-source-software-audit.html https://www.synopsys.com/software-integrity/open-source-soft... At a previous job we had a audit from them, it seemed to not be too accurate but probably good enough for companies to cover their asses legally.
- deleted 5y ago[deleted]