Ask HN: How dangerous is source code access?

Posted by fredrikfornwall on Thursday April 16, 2020 @03:38PM
from the ask-hn dept.

For a small startup whose product requires source code access (think static analysis as a CI service), how dangerous is it having access to the (non-open) source code of commercial customers?

How do we protect ourselves from the risk of a "IP troll" trying to earn money by claiming that we have used their source code, looking for similarities between their code and ours if it comes to a court?

We are planning to have a free tier where anyone can sign up, and without any protective measure it seems that we are opening up ourselves to risk.

At the same time I realise that the situation of having source code access is common (GitHub, GitLab, Travis, Netlify, ...) - how do the big players protect against the same risk, besides having a formidable legal department?

( 1 comment | 8 points | on HN )

Re:Ask HN: How dangerous is source code access? by yellow_lead on Thursday April 16, 2020 @10:23PM (#22895643)

It sounds like you could benefit from a lawyer, some well written terms of use, etc.

Though, I have used a third party tool like this in the past where it did the static analysis locally. Is it out of the question you could do this? Could provide a Jenkins plugin or self-hosted option.

[ Parent | on HN ]