Help
cancel
Showing results for 
Search instead for 
Did you mean: 
Copilot Lvl 2
Message 1 of 3

How to add a license to project my private repository to prevent missuses

We are a small startup. We have onsite and remote developers some are permanent and some are on a contract basis.

 

We want to project our codes. Since a developer can Clone the repository entirely, how could we save it from being utilized w/o our knowledge outside the company? Is adding a license is a solution then how to implement it? Are there any other solutions than signing An NDA because signing an NDA will not work in some portions of the world.

2 Replies
Community Manager
Message 2 of 3

Re: How to add a license to project my private repository to prevent missuses

Hi @itcnj,

 

Thank you for being here! Please keep in mine I'm not an attorney and the information I'm sharing here is external and not a legal recommendation. That out of the way, we created choosealicense.com, to help you understand how to license your code.


Best,
AndreaG

Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!

Copilot Lvl 3
Message 3 of 3

Re: How to add a license to project my private repository to prevent missuses

Hi @itcnj.  

 

I am not aware of any technical way to prevent unintended usage of your repo/code either.

 

However I think that all the solutions you are listing, can help to a certain extend.

Both a LICENSE as well as an NDA are written agreements between you and your developers, that govern how they should treat your repo/code.

 

At the same time, any contract is just trying to fix things that might as well be common-sense or verbal agreements. So they don't give you any guarantees. They just help you in the case you have to go to court, but most people don't really want to do that anyways, right? :)

 

At the end of the day, it comes down to wether you trust the people that you work with or not, and also what the incentive and likelihood of missusing your source code is.

 

One thing that you might want to ask yourself:

(not sure if you can share the answer publicly here, depending on the sensitivity of the matter)

 

What is the absolute worst thing that would happen, if a developer on your team were to keep a copy of your source code, after they are leaving your company? What can they gain from it? What damage can they produce?