Socket.dev

Supported Data Models

Follow the steps below to onboard your environment to our Socket.dev integration.

Generate an API Key

Log in to your Socket.dev dashboard at socket.dev.
If you have multiple organizations, select the correct one from the organization switcher.
Go to Settings → API Keys → Create API Token.
Name it (e.g., “Leen Integration”).
Under Scopes, check:
- repo:list – to list repositories
- alerts:list – to fetch security alerts
Click Create and copy the key (it won’t be shown again).

Copy your API key immediately after creation. It will not be shown again after you close the dialog.

Find Your Organization Slug

In the Socket.dev dashboard, navigate to your organisation’s page.
The organisation slug appears in the URL: https://socket.dev/dashboard/org/{org-slug}/

Enter Configuration Parameters in Leen

In your Leen integration configuration, provide the following:

Parameter	Description	Required
API Token	The API key generated in Step 1.	Yes
Org Slug	Your Socket.dev organisation slug from Step 2.	Yes

Socket alert severities are mapped to Leen’s unified severity model as follows:

Socket alert states are mapped to Leen’s unified state model as follows:

Socket alert categories are mapped to Leen issue and finding types as follows:

The Socket.dev integration syncs the following data:

Alerts: Open security alerts across all repositories, including critical CVEs, supply chain risks, deprecated packages, and potential vulnerabilities.
Repositories: All repositories in the organisation, used as Leen resources of type repository.

For any additional information about our field mappings or integrations, please contact us.