On a serious note, I think it's a smart move to use a name like this, or something like Carrotjuice.js or MochaDB. Names are important and so are the trends that accompany them.
Example: "bingo" Node module. I was thinking of building a simple Bingo game app using Socket.IO, and creating a module that lets it be included in an app. The name is already taken, by a module for .. testing function calls. May be a great project, but how is "bingo" better than "function-introspection". Modules names are pretty much domain squatting.
Next language that comes out with a module system I should grab names like "database" and make the modules randomly post obscenities to Twitter or something equally unrelated.
> Some bug had popped up in this program and the guy assigned to fix it had come back alternatively laughing and crying babbling nonsense about ‘pizzas calling hamburgers and passing booze’.... The software this guy left behind did not have any logic bombs or other nasty tricks in it, it compiled just fine, and besides that one bug it seemed to work fine as well. Imagine this though: every function and variable name in the program was named after food.
Though its probably a bit too late for that now ;-)
You don't need a "cool name"; you need to communicate clearly. Code communicates.
Think spoken language. There's a reason why street slang suggests (wrongly or not) that the speaker is less educated.
Basic bash completion looks for files in the filesystem. The bash-completion package provides hints so that you can auto-complete semantically, for example
$ apt-get up<tab><tab>
$ apt-get install bash<tab><tab>
bash bash-builtins bashburn
bash-completion bashdb bash-doc