1 files changed, 47 insertions, 0 deletions
diff --git a/deps/npm/docs/content/cli-commands/npm-owner.md b/deps/npm/docs/content/cli-commands/npm-owner.md
new file mode 100755
index 0000000000..28660e8926
--- /dev/null
+++ b/deps/npm/docs/content/cli-commands/npm-owner.md
@@ -0,0 +1,47 @@
+---
+section: cli-commands
+title: npm-owner
+description: Manage package owners
+---
+
+# npm-owner
+## Manage package owners
+
+### Synopsis
+
+```bash
+npm owner add <user> [<@scope>/]<pkg>
+npm owner rm <user> [<@scope>/]<pkg>
+npm owner ls [<@scope>/]<pkg>
+
+aliases: author
+```
+
+### Description
+
+Manage ownership of published packages.
+
+* ls:
+  List all the users who have access to modify a package and push new versions.
+  Handy when you need to know who to bug for help.
+* add:
+  Add a new user as a maintainer of a package.  This user is enabled to modify
+  metadata, publish new versions, and add other owners.
+* rm:
+  Remove a user from the package owner list.  This immediately revokes their
+  privileges.
+
+Note that there is only one level of access.  Either you can modify a package,
+or you can't.  Future versions may contain more fine-grained access levels, but
+that is not implemented at this time.
+
+If you have two-factor authentication enabled with `auth-and-writes` then
+you'll need to include an otp on the command line when changing ownership
+with `--otp`.
+
+### See Also
+
+* [npm publish](/cli-commands/npm-publish)
+* [npm registry](/using-npm/registry)
+* [npm adduser](/cli-commands/npm-adduser)
+* [npm disputes](/using-npm/disputes)