Skip to main content

Socket

Monitor your open source supply chain security with Socket. This integration ingests organizations, repositories, software packages and their dependency trees, security alerts, and vulnerability findings to provide visibility into supply chain risks, malware, typosquatting, and known CVEs across your dependencies.

Installation

info

You will need a Socket.dev API key to configure this integration. API keys can be created in the Socket dashboard under Settings > API Keys. See the Socket API documentation for more information.

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

Creating an instance requires the following:

  • API Key - Your Socket.dev API key (Bearer token) used to authenticate requests.

  • Polling Interval - Select a frequency that meets your monitoring needs. You may leave this as DISABLED and manually execute the integration.

Configuration options

Alerts

FieldTypeDescriptionDefault
Alert SeveritiesMulti-selectSelect which alert severities to ingestCritical, High
Alert StatusesMulti-selectSelect which alert statuses to ingestOpen
Alerts Since DaysSelectOnly ingest alerts created in the last N days90

Packages

FieldTypeDescriptionDefault
Include Transitive DependenciesBooleanWhether to ingest transitive (indirect) dependencies from full scans. Enabling this can produce very large graphs.Enabled
RepositoriesStringComma-separated list of repository names to ingest. Leave empty to ingest all repositories.All

What data is ingested?

DataDescription
OrganizationsYour Socket.dev organization account
RepositoriesCode repositories monitored by Socket, with mapped relationships to GitHub repos when the GitHub App is installed
PackagesSoftware packages and dependencies discovered via full scans, including health scores (overall, license, maintenance, quality, supply chain, vulnerability)
Dependency TreesPackage-to-package USES relationships representing the dependency graph within each repository
AlertsSecurity alerts for non-CVE issues (malware, typosquatting, install scripts, etc.)
Vulnerability FindingsCVE-linked vulnerability findings with CVSS scores, CWE IDs, EPSS scores, and KEV status

Required API scopes

The following Socket.dev API scopes are required for full ingestion:

ScopeUsed by
(no extra scope)Listing organizations
repo:listListing repositories
full-scans:listStreaming package data from full scans
alerts:listListing security alerts

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.