Yeah, with the name as-is, `npm` reports this:

```
smash@tiger ~/code/atom-facepalm (master=) $ npm install --save emissary
npm ERR! Error: Invalid name: "Atom Facepalm"
npm ERR!     at ensureValidName (/usr/local/Cellar/node/0.10.26/lib/node_modules/npm/node_modules/read-package-json/node_modules/normalize-package-data/lib/fixer.js:302:15)
npm ERR!     at Object.module.exports.fixNameField (/usr/local/Cellar/node/0.10.26/lib/node_modules/npm/node_modules/read-package-json/node_modules/normalize-package-data/lib/fixer.js:206:5)
npm ERR!     at /usr/local/Cellar/node/0.10.26/lib/node_modules/npm/node_modules/read-package-json/node_modules/normalize-package-data/lib/normalize.js:29:38
```

I guess `apm` isn't quite as picky. It also does some awkward things with the event bindings, though; the configuration keys have a keypath of `'Atom Facepalm.activationEvents'`, for example.