1 files changed, 27 insertions, 1 deletions
diff --git a/deps/npm/man/man7/npm-registry.7 b/deps/npm/man/man7/npm-registry.7
index 2710b1d835..88d802a9dc 100644
--- a/deps/npm/man/man7/npm-registry.7
+++ b/deps/npm/man/man7/npm-registry.7
@@ -1,4 +1,4 @@
-.TH "NPM\-REGISTRY" "7" "November 2016" "" ""
+.TH "NPM\-REGISTRY" "7" "December 2016" "" ""
 .SH "NAME"
 \fBnpm-registry\fR \- The JavaScript Package Registry
 .SH DESCRIPTION
@@ -20,6 +20,32 @@ The registry URL used is determined by the scope of the package (see
 npm help 7 \fBnpm\-scope\fP)\. If no scope is specified, the default registry is used, which is
 supplied by the \fBregistry\fP config parameter\.  See npm help \fBnpm\-config\fP,
 npm help 5 \fBnpmrc\fP, and npm help 7 \fBnpm\-config\fP for more on managing npm's configuration\.
+.SH Does npm send any information about me back to the registry?
+.P
+Yes\.
+.P
+When making requests of the registry npm adds two headers with information
+about your environment:
+.RS 0
+.IP \(bu 2
+\fBNpm\-Scope\fP – If your project is scoped, this header will contain its
+scope\. In the future npm hopes to build registry features that use this
+information to allow you to customize your experience for your
+organization\.
+.IP \(bu 2
+\fBNpm\-In\-CI\fP – Set to "true" if npm believes this install is running in a
+continous integration environment, "false" otherwise\. This is detected by
+looking for the following environment variables: \fBCI\fP, \fBTDDIUM\fP,
+\fBJENKINS_URL\fP, \fBbamboo\.buildKey\fP\|\. If you'd like to learn more you may find
+the original PR \fIhttps://github\.com/npm/npm\-registry\-client/pull/129\fR
+interesting\.
+This is used to gather better metrics on how npm is used by humans, versus
+build farms\.
+
+.RE
+.P
+The npm registry does not to correlate the information in these headers with
+any authenticated accounts that may be used in the same requests\.
 .SH Can I run my own private registry?
 .P
 Yes!