June 13
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:
org
and cwd
. Weβll use stored defaults and prompt you when needed.socket analytics
, socket audit-log
, and socket repository
for simpler, more consistent usage.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
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
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
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.
This gives users more control when they need fresher alert data than the standard update cycle.
June 10
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
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
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
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
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
The Python SDK now supports additional API endpoints for working with labels and historical alert data.
Newly added endpoints include:
π Label Management
π Historical Data
This update makes it easier to automate label workflows and analyze alert history programmatically.