I'm in a bit of a dilemma. A client's tech person wants to check out the code I've been developing, but I'm hesitant to give them full repository access. I need a way to share the code in a view-only format—something that lets them inspect it without the ability to copy, download, or clone. I've come up with a simple solution that displays the code for viewing only and disables copy-paste, but I wonder if there are established tools or methods that can achieve this. Has anyone else experienced something similar? What did you do? Would this kind of solution be useful beyond my current situation? Appreciate any insights!
5 Answers
At the end of the day, if it’s valuable enough, someone will find a way to copy it, regardless of your precautions. Protect yourself legally first, and then if they still insist on seeing it, you’ll need to weigh the risks of losing the client versus potential theft.
I get where you're coming from. But technically, once the code is out, people can always find ways to bypass protections. It's less about the tech and more about trust. If they’re serious about inspecting the code, maybe a screen share would suffice—those are often more than enough for discussions about functionality without giving away full access.
Have you considered showing it in person if that’s an option? Just print it out temporarily, let them look, and then take it back. It’s low-tech but ensures nothing is copied.
A creative workaround could be converting your code into images. It makes it a bit harder for them to copy directly. You could try using a service that turns code into stylized images, but keep in mind that even that isn’t foolproof.
Honestly, it's a tough situation. Once you show your code to someone, there’s always a risk they can copy it. Even a simple screenshot can turn into a problem. Legal agreements like NDAs are really the best way to protect yourself. If they haven’t paid yet, I’d be a bit suspicious of their intentions.
That's the thing, right? They want to see your work before paying, which raises red flags. Maybe suggest a split payment plan instead?
That's a neat idea! But what if they want to navigate through it? Making it image-based limits interaction.