πŸš€ Big News: Socket Acquires Coana to Bring Reachability Analysis to Every Appsec Team.Learn more β†’
Socket
DemoInstallSign in
Socket

Changelog

What's new at Socket?

June 13

Socket CLI v1 Released

Socket CLI v1 is here! This release streamlines and simplifies the command-line experience with cleaner defaults, improved ergonomics, and includes several breaking changes.

Highlights:

  • Dropped the need to manually pass org and cwd. We’ll use stored defaults and prompt you when needed.
  • Reworked commands like socket analytics, socket audit-log, and socket repository for simpler, more consistent usage.
  • Deprecated older commands in favor of new ones like socket scan diff, socket package score, and socket scan report.

This is now the default experience for everyone using the CLI. View the full migration guide for detailed changes and command updates.

New to the CLI?
Get started by installing Socket CLI on npm and reading the CLI docs. It’s the fastest way to automate scans, view threats, and manage your Socket org from the terminal.

June 12

Improved Accuracy and Efficiency in Maven SBOM Calculation

We have dramatically improved accuracy and efficiency in Maven SBOM calculation. The vast majority of noise has been eliminated (~90+% noise reduction).

We now miss fewer compile time dependencies while collecting far fewer development dependencies. This plus a few other optimizations result in much faster SBOM resolution times - typically 10–100x faster (outpacing a cold-cache mvn dependency:tree on large projects).

As part of these changes, we've also improved support for:

- import scopes (BOM imports)

- exclusions

- dependencyManagement

- property inheritance

Check out our ecosystem support docs for a full overview of our Java support.

June 12

Redesigned Dashboard Now Live for All Users

We’ve rolled out our redesigned dashboard to all Socket users!
The new layout improves focus with a cleaner visual hierarchy, collapsible sections, and a refreshed color scheme that’s optimized for focusing.

June 12

New: Manual Alert Refresh Button

You can now manually refresh alert data from the Alerts page.
Click the β€œβ€¦β€ menu in the top-right corner and select Request refresh to get the latest snapshot.

  • Refreshes are rate-limited:
    β€’ Enterprise: once every 6 hours
    β€’ Team: once every 12 hours
  • We’ll show you the time of the last refresh
  • You’ll see an error if you hit the rate limit

This gives users more control when they need fresher alert data than the standard update cycle.

June 10

Python CLI: More Reliable Full Scan Polling

We’ve improved how the Socket Python CLI handles full scans.
Instead of relying on long-running connections, the CLI now polls for scan readiness before running a diff.

This makes it more resilient in environments where idle connections might be cut off by network settings.

June 10

Fix: Archived GitHub Repos No Longer Re-Created on Socket

We fixed a bug where archived GitHub repos in a user's Socket GitHub App installation were being re-created on Socket after deletion.
We now skip archived repos during sync, so deleted ones stay gone.

June 5

New: Filter Alerts by Action Source

You can now filter alerts by action source in the alert table, making it easier to distinguish between alerts triaged manually and those resolved automatically by security policies.

To use this feature, click Filter β†’ Alert Action Source. This is especially helpful for answering questions like, β€œWhich alerts did I triage myself?”

This change also removes the deprecated policy coverage filter, which is no longer needed with the improved alert visibility.

June 4

Support for pylock.toml (PEP 751) Now Available

Socket now fully supports pylock.toml, the new standardized Python lock file format introduced in PEP 751. This enables secure, reproducible builds and allows Socket to provide precise, hash-based security analysis for Python projects using the latest ecosystem tooling.

If your project includes a pylock.toml and pyproject.toml, Socket will automatically detect and analyze it in your next scan.

πŸ‘‰ Read the full announcement for more details on the benefits of using pylock.toml and instructions on how to migrate.

June 4

New: Rename Repository Labels via API

You can now rename repository labels through the API as well as the UI.

In the UI, click the "…" next to any label in your repository's label list, then select Edit to change its name.
To rename a label via the API, use the new PUT method on the label endpoint. This operation requires the repo-label:update scope.

This update ensures consistent label management across both the UI and API.

June 2

Python SDK: Added Support for Historical and Label Endpoints

The Python SDK now supports additional API endpoints for working with labels and historical alert data.

Newly added endpoints include:

πŸ”– Label Management

  • Create, list, get, delete labels
  • Associate or disassociate labels with alerts
  • Manage label settings (get, update, delete)

πŸ“Š Historical Data

  • List past alerts
  • View alert trends over time
  • List and create alert snapshots

This update makes it easier to automate label workflows and analyze alert history programmatically.