NPM

Visualize NPM users, groups, and packages, map NPM users to employees, and monitor changes through queries and alerts.

Installation guide

Installation

info

For this integration, you will need to create an NPM token with Read only access. See their documentation for more information.

Configuration in JupiterOne

To install the NPM integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select NPM. Click New Instance to begin configuring your integration.

Creating a configuration requires the following:

• The Account Name used to identify the NPM account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

• Description to assist in identifying the integration instance, if desired.

• Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.

• Your NPM Organization and Access Token (configured for read access).

Click Create once all values are provided to finalize the integration.

Next steps

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.

NPM data model

Data Model

Entities

The following entities are created:

Resources	Entity _type	Entity _class
Package	npm_package	CodeModule
Team	npm_team	UserGroup
User	npm_user	User

Relationships

The following relationships are created:

Source Entity _type	Relationship _class	Target Entity _type
npm_team	HAS	npm_user