Hiding source code in the project

[vivid meteor]

you can obfuscate, try to build to il2pp but in the end, everything that the client has on their device can be decompiled.
I'd recommend having a good NDA in your contract for this,
as for projects, my old company handled permission for projects on a user basis, so regardless if you self host your git repo or you have an external host, only add the user of the intern to the projects they actually have to work on

I've seen people that reconstructed whole projects from windows builds. Models, scenes.
shaders might not be possible, not sure. I haven't modded unity before, but if you look for unity modding and decompiling, you might see some people doing that with popular projects

in the project itself, I don't think so

what you could do is to make sub-git repositories

so separate folders in your project might be their own git repository, and you can instruct the interns to set up an empty project for this and then add the library/folder as submodule. that way you could only expose certain parts.
but I'm wondering if that is even useful, if they can only work in a secluded environment (and someone else integrated their changes in the main project)

a dll file is only scripts

and Monobehaviour is a script too, there is no difference between that and a "pure c# class"

but a dll can be easy to decompile as well

also, is your company looking for other applicants outside of interns?

out of curiosity

[mint glade]

Thank you @vivid meteor , NDA is indeed present! Seperate git repos might have been a good strategy only its too bad we made the mistake of using plastic

[grand rain]

Jego thanked fmproductions

[mint glade]

Not at the moment, is a start-up with low revenue so there's a reason they're interns

[vivid meteor]

ah yeah, that's a good reason.

I never worked with plastic, so I can't tell how to set that up

if you manage to do it, and you're really scared about the reproduction, you might have to clean the past commits where those files where included in the main project I imagine

otherwise they could restore an old project version and have access to the files

or maybe for their first tasks, you could give them some package that they install locally and someone more experienced will then take their work/project at the end and integrates the changes in the main one

[mint glade]

past commits are another consideration indeed, not too worried about people going out of their way with malicious intent, simply don't want to make it too easy for them

am taking a closer look at dlls since they look like the way to go, thanks again for your replies