New:Introducing Socket Scanning for VS Code Marketplace Extensions.Learn more →
Get Started

Changelog

What's new at Socket?

November 19

Expanded Java Coverage and More Accurate Reachability Results

Full application reachability analysis now covers more Java application code, with accuracy and performance improvements across JavaScript, TypeScript, Python, Rust, and Go.

  • Expanded Java coverage: Socket now analyzes Android libraries packaged as AARs and follows Spring Boot auto-configuration, Spring XML bean definitions, service loading, JPA and servlet descriptors, and calls from Java into Scala objects.
  • More accurate Java results: Vulnerabilities in libraries Socket couldn’t analyze now show Unknown. When a vulnerability pattern doesn’t match the package, Socket falls back to precomputed results. Both fixes address cases that previously produced an incorrect Unreachable result.
  • Correct Rust call stacks: Projects using multiple versions of a crate now get call stacks specific to each version.
  • Analysis performance and precision: JavaScript, TypeScript, and Python analysis gains accuracy and performance improvements, particularly for Python projects using PyTorch. Go analysis also improves performance and fixes a rare issue that caused excessive memory use.
  • Socket token isolation: Package managers and build tools launched during reachability analysis or socket fix no longer inherit the Socket API token or Socket-specific environment settings. docs.socket.dev

These improvements ship in reachability engine 15.15.2, included in Socket Python CLI v2.12.2. See the full reachability changelog for additional fixes.

November 18

Fix: Nginx Security Updates in Socket Registry Firewall

Socket Registry Firewall v2.21.1 updates its Docker images with nine security fixes backported from nginx 1.31.9, addressing vulnerabilities in the firewall’s underlying web server.

Upgrade to Socket Registry Firewall v2.21.1 to apply these fixes to your deployment.

November 17

Get Notified When Webhook Deliveries Fail

Socket now emails your organization’s Owners and Admins when every delivery to an outbound webhook has failed for 12 hours. The notification includes the scheduled disable date, giving your team time to fix the endpoint. After four days of continuous failures, Socket disables the webhook and sends another email.

The webhooks table helps you track affected endpoints:

  • Unhealthy: The webhook is still active, but Socket has scheduled it for disabling. Hover over the badge to see the date. A successful delivery clears the badge.
  • Deliveries failing: Socket has disabled the webhook. The badge shows when this happened.

After fixing the endpoint, set the webhook back to Active to resume deliveries. Previous failures no longer count toward automatic disabling.

November 17

New: Malware Scanning for Terraform, HCL, and CMake

Socket now scans infrastructure configuration and build files for malware, expanding coverage to Terraform and HCL files (.tf, .tfvars, .hcl) and CMake files (CMakeLists.txt, .cmake).

Socket analyzes these files for behaviors such as running commands, downloading content, and accessing environment variables, with AI analysis for potentially risky files. For npm packages whose install scripts run cmake or cmake-js, Socket also analyzes CMake files as part of the installation behavior.

CMake coverage applies to package versions analyzed after November 17.

November 17

More Reliable Managed Reachability Scans for Rust

Socket’s managed reachability environment now includes an updated Rust toolchain and native build dependencies, so more Rust projects can build successfully for analysis.

This update resolves Analysis Error failures caused by missing C and C++ build tools, OpenSSL headers, or an outdated Rust toolchain.

November 17

Fix: Deep Rescans Apply Your Current Dependency Limit

Deep rescans now use your organization’s current dependency limit. After upgrading your plan, you can rescan a previously truncated scan to include more dependencies, up to your new limit.

Previously, deep rescans reused the limit from when the scan was first created, leaving dependencies out even after an upgrade. Shallow rescans are unchanged.

November 16

Socket Basics 3.5.0: Reachability and Proxy Updates

Socket Basics 3.5.0 improves proxy support and argument handling for Enterprise customers running full application reachability analysis. Existing setups may need configuration changes before upgrading.

  • New network requirements: Full application reachability scans now require outbound access to api.socket.dev and storage.googleapis.com. Socket downloads the reachability engine directly instead of through npm, with no npm fallback. An npm mirror alone is no longer sufficient, and SOCKET_CLI_COANA_LAUNCHER no longer takes effect. Older engine versions released before this change cannot be used with --reach-version.
  • More reliable argument handling:socket_additional_params now preserves commas and quoted spaces within values, so options such as --reach-ecosystems=npm,pypi work correctly. Use --reach-analysis-timeout=90s instead of --reach-analysis-timeout,90s, and pass multiple exclusions using repeated --exclude-paths flags.
  • Proxy support: Reachability scans now honor HTTPS_PROXY and NO_PROXY, making it easier to run scans behind a corporate proxy.

This release also updates the reachability engine to Coana 15.15.0.

View the Socket Basics 3.5.0 release notes.

November 16

Improved SPDX and CycloneDX SBOM Exports

Socket’s SBOM exports now work more reliably with validators and downstream tools, with fixes to package identifiers, dependency relationships, and Ruby gem versions.

  • SPDX: Valid, unique package identifiers fix validation failures affecting npm and Bundler projects. Exports now use DEPENDS_ON relationships from the project to its dependencies and include supplier information when the publisher is known, or NOASSERTION otherwise.
  • CycloneDX: Exports now include the project’s direct dependencies.
  • Ruby gems: Gems with platform-specific builds, such as nokogiri, now appear once for each platform locked in Gemfile.lock. Each entry uses the registry version and a platform qualifier, helping other tools match it correctly.

If your integration reads DEPENDENCY_OF relationships from Socket’s SPDX exports, update it to read DEPENDS_ON. The first diff scan after this update will show affected platform-specific gems as removed and re-added once.

November 13

New alert covering dual use tools

New “Dual-use functionality” alert that flags packages which are legitimate security research or testing tools, such as offensive security, penetration testing, or vulnerability research tooling. While not inherently malicious, their capabilities can be misused for unauthorized purposes, Organizations with strict security or compliance requirements may want to review them before allowing them in their environments.

November 13

SBOM Exports Now Show Socket Patch Fixes

CycloneDX and SPDX exports now include applied Socket patches and the advisories they resolve, making it easier to share remediation evidence with auditors and downstream security tools. Previously, exports could show patched packages as still vulnerable.

  • CycloneDX: Each patched component includes a link to its patch and the advisories it fixes. With include_vulnerabilities=true, those vulnerabilities carry the analysis state resolved_with_pedigree for the patched component.
  • SPDX 2.3: Patched packages include a patch link and the advisories it fixes. Pair the document with an OpenVEX export for machine-readable vulnerability status.

Exports exclude withdrawn patches. Package identifiers remain unchanged, so downstream tools need to read the patch evidence and vulnerability analysis to recognize the fixes.