npm-profile
Advanced tools
Updating an npmjs.com profile
const profile = require('npm-profile')
profile.get(registry, {token}).then(result => {
// …
})
profile.adduser(username, email, password, {registry}).then(result => {
// do something with result.token
})
Creates a new user on the server along with a fresh bearer token for future
authentication as this user. This is what you see as an authToken in an
.npmrc.
If the user already exists then the npm registry will return an error, but this is registry specific and not guaranteed.
username Stringemail Stringpassword Stringconfig Object
registry String (for reference, the npm registry is https://registry.npmjs.org)opts Object, make-fetch-happen options for setting
things like cache, proxy, SSL CA and retry rules.An object with a token property that can be passed into future authentication requests.
An error object indicating what went wrong.
The headers property will contain the HTTP headers of the response.
If the action was denied because an OTP is required then code will be set
to otp.
If the action was denied because it came from an IP address that this action
on this account isn't allowed from then the code will be set to ipaddress.
Otherwise the code will be the HTTP response code.
profile.login(username, password, {registry}).catch(err => {
if (err.code === 'otp') {
return getOTPFromSomewhere().then(otp => {
return profile.login(username, password, {registry, auth: {otp}})
})
}
}).then(result => {
// do something with result.token
})
Logs you into an existing user. Does not create the user if they do not
already exist. Logging in means generating a new bearer token for use in
future authentication. This is what you use as an authToken in an .npmrc.
username Stringemail Stringpassword Stringconfig Object
registry String (for reference, the npm registry is https://registry.npmjs.org)auth Object, properties: otp — the one-time password from a two-factor
authentication device.opts Object, make-fetch-happen options for setting
things like cache, proxy, SSL CA and retry rules.An object with a token property that can be passed into future authentication requests.
An error object indicating what went wrong.
If the object has a code property set to otp then that indicates that
this account must use two-factor authentication to login. Try again with a
one-time password.
If the object has a code property set to ip then that indicates that
this account is only allowed to login from certain networks and this ip is
not on one of those networks.
If the error was neither of these then the error object will have a
code property set to the HTTP response code and a headers property with
the HTTP headers in the response.
profile.get(registry, {auth: {token}}).then(userProfile => {
// do something with userProfile
})
Fetch profile information for the authenticated user.
config Object
registry String (for reference, the npm registry is https://registry.npmjs.org)auth Object, properties: token — a bearer token returned from
adduser, login or createToken, or, username, password (and
optionally otp). Authenticating for this command via a username and
password will likely not be supported in the future.opts Object, make-fetch-happen options for setting
things like cache, proxy, SSL CA and retry rules.An object that looks like this:
// "*" indicates a field that may not always appear
{
tfa: null |
false |
{"mode": "auth-only", pending: Boolean} |
["recovery", "codes"] |
"otpauth://...",
name: String,
email: String,
email_verified: Boolean,
created: Date,
updated: Date,
cidr_whitelist: null | ["192.168.1.1/32", ...],
fullname: String, // *
homepage: String, // *
freenode: String, // *
twitter: String, // *
github: String // *
}
An error object indicating what went wrong.
The headers property will contain the HTTP headers of the response.
If the action was denied because an OTP is required then code will be set
to otp.
If the action was denied because it came from an IP address that this action
on this account isn't allowed from then the code will be set to ipaddress.
Otherwise the code will be the HTTP response code.
profile.set({github: 'great-github-account-name'}, {registry, auth: {token}})
Update profile information for the authenticated user.
profileData An object, like that returned from profile.get, but see
below for caveats relating to password, tfa and cidr_whitelist.config Object
registry String (for reference, the npm registry is https://registry.npmjs.org)auth Object, properties: token — a bearer token returned from
adduser, login or createToken, or, username, password (and
optionally otp). Authenticating for this command via a username and
password will likely not be supported in the future.opts Object, make-fetch-happen options for setting
things like cache, proxy, SSL CA and retry rules.passwordThis is used to change your password and is not visible (for obvious
reasons) through the get() API. The value should be an object with old
and new properties, where the former has the user's current password and
the latter has the desired new password. For example
profile.set({password: {old: 'abc123', new: 'my new (more secure) password'}}, {registry, auth: {token}})
cidr_whitelistThe value for this is an Array. Only valid CIDR ranges are allowed in it.
Be very careful as it's possible to lock yourself out of your account with
this. This is not currently exposed in npm itself.
profile.set({cidr_whitelist: [ '8.8.8.8/32' ], {registry, auth: {token}})
// ↑ only one of google's dns servers can now access this account.
tfaEnabling two-factor authentication is a multi-step process.
profile.get and check the status of tfa. If pending is true then
you'll need to disable it with profile.set({tfa: {password, mode: 'disable'}, …).profile.set({tfa: {password, mode}}, {registry, auth: {token}})
password is required here in the tfa object,
regardless of how you're authenticating.mode is either auth-only which requires an otp when calling login
or createToken, or mode is auth-and-writes and an otp will be
required on login, publishing or when granting others access to your
modules.tfa property set to an otpauth URL, as
used by Google Authenticator.
You will need to show this to the user for them to add to their
authenticator application. This is typically done as a QRCODE, but you
can also show the value of the secret key in the otpauth query string
and they can type or copy paste that in.profile.set with tfa set to an array of TWO codes from the user's
authenticator, eg: profile.set(tfa: [otp1, otp2]}, registry, {token})tfa property that has an
array of one-time-use recovery codes. These are used to authenticate
later if the second factor is lost and generally should be printed and
put somewhere safe.Disabling two-factor authentication is more straightforward, set the tfa
attribute to an object with a password property and a mode of disable.
profile.set({tfa: {password, mode: 'disable'}, {registry, auth: {token}}}
An object reflecting the changes you made, see description for profile.get.
An error object indicating what went wrong.
The headers property will contain the HTTP headers of the response.
If the action was denied because an OTP is required then code will be set
to otp.
If the action was denied because it came from an IP address that this action
on this account isn't allowed from then the code will be set to ipaddress.
Otherwise the code will be the HTTP response code.
profile.listTokens(registry, {token}).then(tokens => {
// do something with tokens
})
Fetch a list of all of the authentication tokens the authenticated user has.
config Object
registry String (for reference, the npm registry is https://registry.npmjs.org)auth Object, properties: token — a bearer token returned from
adduser, login or createToken, or, username, password (and
optionally otp). Authenticating for this command via a username and
password will likely not be supported in the future.opts Object, make-fetch-happen options for setting
things like cache, proxy, SSL CA and retry rules.An array of token objects. Each token object has the following properties:
An error object indicating what went wrong.
The headers property will contain the HTTP headers of the response.
If the action was denied because an OTP is required then code will be set
to otp.
If the action was denied because it came from an IP address that this action
on this account isn't allowed from then the code will be set to ipaddress.
Otherwise the code will be the HTTP response code.
profile.removeToken(key, registry, {token}).then(() => {
// token is gone!
})
Remove a specific authentication token.
token|key String, either a complete authentication token or the key returned by profile.listTokens.config Object
registry String (for reference, the npm registry is https://registry.npmjs.org)auth Object, properties: token — a bearer token returned from
adduser, login or createToken, or, username, password (and
optionally otp). Authenticating for this command via a username and
password will likely not be supported in the future.opts Object, make-fetch-happen options for setting
things like cache, proxy, SSL CA and retry rules.No value.
An error object indicating what went wrong.
The headers property will contain the HTTP headers of the response.
If the action was denied because an OTP is required then code will be set
to otp.
If the action was denied because it came from an IP address that this action
on this account isn't allowed from then the code will be set to ipaddress.
Otherwise the code will be the HTTP response code.
profile.createToken(password, readonly, cidr_whitelist, registry, {token, otp}).then(newToken => {
// do something with the newToken
})
Create a new authentication token, possibly with restrictions.
password Stringreadonly Booleancidr_whitelist Arrayconfig Object
registry String (for reference, the npm registry is https://registry.npmjs.org)auth Object, properties: token — a bearer token returned from
adduser, login or createToken, or, username, password (and
optionally otp). Authenticating for this command via a username and
password will likely not be supported in the future.opts Object, make-fetch-happen options for setting
things like cache, proxy, SSL CA and retry rules.The promise will resolve with an object very much like the one's returned by
profile.listTokens. The only difference is that token is not truncated.
{
token: String,
key: String, // sha512 hash of the token UUID
cidr_whitelist: [String],
created: Date,
readonly: Boolean
}
An error object indicating what went wrong.
The headers property will contain the HTTP headers of the response.
If the action was denied because an OTP is required then code will be set
to otp.
If the action was denied because it came from an IP address that this action
on this account isn't allowed from then the code will be set to ipaddress.
Otherwise the code will be the HTTP response code.
FAQs
Library for updating an npmjs.com profile
The npm package npm-profile receives a total of 259,995 weekly downloads. As such, npm-profile popularity was classified as popular.
We found that npm-profile demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 6 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.