{"action":"created","issue":{"url":"https://api.github.com/repos/npm/npm/issues/8291","labels_url":"https://api.github.com/repos/npm/npm/issues/8291/labels{/name}","comments_url":"https://api.github.com/repos/npm/npm/issues/8291/comments","events_url":"https://api.github.com/repos/npm/npm/issues/8291/events","html_url":"https://github.com/npm/npm/issues/8291","id":77161662,"number":8291,"title":"npm init for closed source modules","user":{"login":"kesla","id":74128,"avatar_url":"https://avatars.githubusercontent.com/u/74128?v=3","gravatar_id":"","url":"https://api.github.com/users/kesla","html_url":"https://github.com/kesla","followers_url":"https://api.github.com/users/kesla/followers","following_url":"https://api.github.com/users/kesla/following{/other_user}","gists_url":"https://api.github.com/users/kesla/gists{/gist_id}","starred_url":"https://api.github.com/users/kesla/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kesla/subscriptions","organizations_url":"https://api.github.com/users/kesla/orgs","repos_url":"https://api.github.com/users/kesla/repos","events_url":"https://api.github.com/users/kesla/events{/privacy}","received_events_url":"https://api.github.com/users/kesla/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/npm/npm/labels/documentation","name":"documentation","color":"d105f0"},{"url":"https://api.github.com/repos/npm/npm/labels/feature-request","name":"feature-request","color":"ACE1AF"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":27,"created_at":"2015-05-16T23:47:16Z","updated_at":"2015-11-08T23:49:32Z","closed_at":"2015-06-19T21:31:08Z","body":"I've had the habit of setting license to `closed` for closed (work) modules.\r\n\r\nIn the latest version of npm that's not possible, and simply pressing enter will set the default license (ISC). Can I use `npm init` somehow for these closed source modules without needing to go in and remove the attribute afterwards?"},"comment":{"url":"https://api.github.com/repos/npm/npm/issues/comments/154887420","html_url":"https://github.com/npm/npm/issues/8291#issuecomment-154887420","issue_url":"https://api.github.com/repos/npm/npm/issues/8291","id":154887420,"user":{"login":"vmadman","id":1026490,"avatar_url":"https://avatars.githubusercontent.com/u/1026490?v=3","gravatar_id":"","url":"https://api.github.com/users/vmadman","html_url":"https://github.com/vmadman","followers_url":"https://api.github.com/users/vmadman/followers","following_url":"https://api.github.com/users/vmadman/following{/other_user}","gists_url":"https://api.github.com/users/vmadman/gists{/gist_id}","starred_url":"https://api.github.com/users/vmadman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vmadman/subscriptions","organizations_url":"https://api.github.com/users/vmadman/orgs","repos_url":"https://api.github.com/users/vmadman/repos","events_url":"https://api.github.com/users/vmadman/events{/privacy}","received_events_url":"https://api.github.com/users/vmadman/received_events","type":"User","site_admin":false},"created_at":"2015-11-08T23:49:32Z","updated_at":"2015-11-08T23:49:32Z","body":"@benoitrolland\r\n\r\n> But If you want to protect your code, you need to systematically setup a specific licence configuration even for your tests in case your code would leek on the net.\r\n\r\nFirst, I'm not an attorney nor do I claim to be qualified to give legal advice.  You should contact an attorney if you find yourself in a position in which licensing, copyrights, or intellectual property rights matter.  With that said:\r\n\r\nThe thing to remember is that all code not explicitly released to the public domain is, by default, copyright and protected.  You just have to realize that if your code is leaked, and it's useful to someone else, they can use it regardless of what license you write in any file.\r\n\r\nYou just have to consider what, exactly, you're trying to protect your code from.  First, keep in mind that your code is probably not worth protecting in the first place.  Value is source code comes from the planning and ongoing support and maintenance of the software.\r\n\r\nSo, if you're trying to protect your code from independent developers, just don't bother... at the end of the day, it's just not going to matter.\r\n\r\nSomething actually worth protecting against, though, is mid-to-large sized companies.  They have a lot to lose and, usually, they are more concerned about the license for an OSS component than the author is.  Very few of them would even use your code, for any purpose, without first finding an explicitly license telling them that they can do so.\r\n\r\nOf course, though, if they do not care about licenses... then it doesn't matter anyway, they'll use it and you can't stop them, except by, of course, not leaking your code in the first place.\r\n\r\nAt the end of the day OSS licenses provide assurance to people who want to honestly and fairly use your source.  Licenses do not protect against people who have no regard for intellectual property rights.\r\n\r\nIn other words.. just do your best to affix the appropriate license information to your source and don't worry too much about the rest."}}