Enterprise Propietary Software Solutions

What are some ways by which Enterprises safeguard against the risks of proprietary software?

I know there must be both legal and technical safeguards. I'm interested in the latter.

The reason I'm mainly asking this is: Say I have an office utility software suit that some BigName employees might greatly benefit from. Say that I'm well connected to some BigName software house to be able to pitch the software to the would be consumers. How do I assure them that my software is safe without actually revealing the source code?

>>9
Where does K&R say that a C program shouldn't be more than 10 lines?

The FreeBSD and GNU versions of echo has more features than the Unix version. That means more code. So what? What does that have to do with knowing C and using it correctly? Is the code incorrect? Are there buffer overflows?

Take your Github ``gist'' back to whence you came: Hacker News

>>9
The GNU version is best. none of the other's implement --help to print the program's usage, including specifics on the (also not implemented) -E and -e options, which are useful depending on how your script uses echo. Also, vs the SYS V and other older versions, this version of echo doesn't require a shell to properly handle escape sequences or quotes. It also properly detects and uses locales and characters sets. The FreeBSD version does almost none of these things. Also, given the source code above, it would be a simple matter to reimplement echo more simply. Be careful. Some of that extra functionality may be neccesary for your system to function.