Because directory names cannot contain slashes, npm init will never default to an npm-2-style scoped package name:

» mkdir -p @zeke/some-package
» cd @zeke/some-package 
» npm init
This utility blah blah...
name: (some-package) 

It might be cool if npm init suggested @zeke/somepackage, but probably not. Plus who's gonna create a directory name starting with an @? No one, that's who.

Or what about a flag or npm-config setting, like npm init --scope=@zeke?

Bah. Feel free to close this issue upon reading.