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.