@ -175,51 +175,54 @@ help config</code> to learn about all the options you can set there.</p>
< h2 id = "More-Docs" > More Docs< / h2 >
< p > Check out the < a href = "https://npmjs.org/doc/" > docs< / a > ,
especially the < a href = "https://npmjs.org/doc/faq.html" > faq< / a > .< / p >
< p > Check out the < a href = "https://www. npmjs.org/doc/" > docs< / a > ,
especially the < a href = "https://www. npmjs.org/doc/faq.html" > faq< / a > .< / p >
< p > You can use the < code > npm help< / code > command to read any of them.< / p >
< p > If you' re a developer, and you want to use npm to publish your program,
you should < a href = "https://npmjs.org/doc/developers.html" > read this< / a > < / p >
you should < a href = "https://www. npmjs.org/doc/developers.html" > read this< / a > < / p >
< h2 id = "Legal-Stuff" > Legal Stuff< / h2 >
< p > " npm" and " the npm registry" are owned by Isaac Z. Schlueter .
< p > " npm" and " The npm Registry" are owned by npm, Inc .
All rights reserved. See the included LICENSE file for more details.< / p >
< p > " Node.js" and " node" are trademarks owned by Joyent, Inc. npm is not
officially part of the Node.js project, and is neither owned by nor
officially affiliated with Joyent, Inc.< / p >
< p > " Node.js" and " node" are trademarks owned by Joyent, Inc.< / p >
< p > The packages in the npm registry are not part of npm itself, and are the
sole property of their respective maintainers. While every effort is
made to ensure accountability, there is absolutely no guarantee,
warrantee, or assertion made as to the quality, fitness for a specific
purpose, or lack of malice in any given npm package. Modules
published on the npm registry are not affiliated with or endorsed by
Joyent, Inc., Isaac Z. Schlueter, Ryan Dahl, or the Node.js project.< / p >
< p > Modules published on the npm registry are not officially endorsed by
npm, Inc. or the Node.js project.< / p >
< p > If you have a complaint about a package in the npm registry, and cannot
resolve it with the package owner, please express your concerns to
Isaac Z. Schlueter at < a href = "mailto:i@izs.me" > i@izs.me< / a > .< / p >
< p > Data published to the npm registry is not part of npm itself, and is
the sole property of the publisher. While every effort is made to
ensure accountability, there is absolutely no guarantee, warrantee, or
assertion expressed or implied as to the quality, fitness for a
specific purpose, or lack of malice in any given npm package.< / p >
< h3 id = "In-plain-english" > In plain english< / h3 >
< p > If you have a complaint about a package in the public npm registry,
and cannot < a href = "https://www.npmjs.org/doc/misc/npm-disputes.html" > resolve it with the package
owner< / a > , please email
< a href = "mailto:support@npmjs.com" > support@npmjs.com< / a > and explain the situation.< / p >
< p > This is mine; not my employer' s, not Node' s, not Joyent' s, not Ryan
Dahl' s.< / p >
< p > Any data published to The npm Registry (including user account
information) may be removed or modified at the sole discretion of the
npm server administrators.< / p >
< h3 id = "In-plainer-english" > In plainer english< / h3 >
< p > npm is the property of npm, Inc.< / p >
< p > If you publish something, it' s yours, and you are solely accountable
for it. Not me, not Node, not Joyent, not Ryan Dahl.< / p >
for it.< / p >
< p > If other people publish something, it' s theirs. Not mine, not Node' s,
not Joyent' s, not Ryan Dahl' s.< / p >
< p > If other people publish something, it' s theirs.< / p >
< p > Yes, you can publish something evil. It will be removed promptly if
reported, and we' ll lose respect for you. But there is no vetting
process for published modules .< / p >
< p > Users can publish Bad Stuff. It will be removed promptly if reported.
But there is no vetting process for published modules, and you use
them at your own risk. Please inspect the source .< / p >
< p > If this concerns you, inspect the source before using packages.< / p >
< p > If you publish Bad Stuff, we may delete it from the registry, or even
ban your account in extreme cases. So don' t do that.< / p >
< h2 id = "BUGS" > BUGS< / h2 >
@ -239,7 +242,7 @@ will no doubt tell you to put the output in a gist or email.</p>
< ul > < li > < a href = "cli/npm.html" > npm(1)< / a > < / li > < li > < a href = "misc/npm-faq.html" > npm-faq(7)< / a > < / li > < li > < a href = "cli/npm-help.html" > npm-help(1)< / a > < / li > < li > < a href = "misc/npm-index.html" > npm-index(7)< / a > < / li > < / ul >
< / div >
< p id = "footer" > < a href = "../doc/README.html" > README< / a > — npm@1.4.0 < / p >
< p id = "footer" > < a href = "../doc/README.html" > README< / a > — npm@1.4.3 < / p >
< script >
;(function () {
var wrapper = document.getElementById("wrapper")
isaacs
11 years ago
Timothy J Fontaine