Changelog

Stay updated with the latest features and improvements

September 14, 2025

CLIv1.5.0

September 14, 2025

Instant descriptor updates on VSCode and analyzer improvements

This release continues the real-time improvements from version 1.3.0. Both descriptors and assets views now update in real-time, significantly improving the user experience. Please update the VSCode extension to version 1.4.0 to get the latest features.

Instant Descriptor Updates in VSCode

jxscout now emits updates of discovered descriptors incrementally to VSCode.

This completes the real-time updates implementation for the VSCode extension.

New Secret Analyzers

Added a secret detector that identifies sensitive variable names.
Added a secret detector that identifies high-entropy strings.

Other Improvements and Bug Fixes

Fixed an edge case where chunks were not downloaded when the server responded with Content-Encoding but didn't actually encode the content.
Fixed an edge case where analysis failed when some identified matches contained invalid JSON characters.
Fixed scenarios where the paths analyzer generated duplicate matches for string concatenation (e.g., '/api'.concat('/users') would match both 'api' and 'api'.concat('users')).
The optimizer now uses the same prettier settings as regular files, avoiding duplicate findings.

VSCode Extensionv1.4.0

September 14, 2025

Instant descriptor updates support and other improvements

This release includes support for instant descriptor updates and other improvements. Please update the CLI version to 1.5.0 as well to get the latest features.

Added support for instant descriptor updates. jxscout will now emit descriptor updates incrementally to VSCode.
You can now right-click on the assets view to filter descriptors.
Added counts to the assets view.

August 31, 2025

CLIv1.4.0

August 31, 2025

Automatic Next.js Chunk Discovery, instant updates on VSCode, and other improvements

This is a big release that includes UX improvements, bug fixes, and new features. Please update the VSCode version to 1.3.0 as well to get the latest features.

Next.js Chunk Discovery

jxscout now automatically finds _buildManifest.js files and analyzes them to find lazy loaded chunks.

This will greatly improve your coverage on Next.js applications.

Instant Asset Updates on VSCode

jxscout will now emit updates of discovered assets incrementally to VSCode.

This is the first step towards a better UX where you will see real-time updates in VSCode without needing to refresh the views.

Other Improvements and Bug Fixes

Fixed a bug in asset relationship tracking where JavaScript files that load other JavaScript files were not being tracked.
Fixed an edge case in the chunk discoverer where certain chunks were not being detected.
Fixed a bug in sourcemap reversal where reversed sources were being written to locations outside the sourcemaps directory.

VSCode Extensionv1.3.0

August 31, 2025

Instant asset updates support and other improvements

This release includes support for instant asset updates and other improvements. Please update the CLI version to 1.4.0 as well to get the latest features.

Added support for instant asset updates. jxscout will now emit updates of discovered assets incrementally to VSCode.
You can now copy asset URLs to the clipboard by right-clicking on assets in the asset view.
Improved fuzzy matching for asset search.

August 11, 2025

CLIv1.3.0

August 11, 2025

CLI client introduction and optimizer improvements

This release introduces a new CLI for extracting information from jxscout and includes optimizer improvements.

CLI client

You can now use jxscout -c to enter client mode.

This provides an alternative way to extract information from jxscout without using the VSCode extension. Here are some example commands:

$ jxscout -c descriptors --descriptor-types paths # Returns all paths found in the current project

$ jxscout -c descriptors --descriptor-types graphql # Returns all GraphQL queries and mutations found in the current project

$ jxscout -c js-files -only-chunks --print-urls # Prints the URLs of all webpack chunks found

Optimizer Improvements

The previous optimizer I created for the MVP was very memory and CPU intensive. This release took a while because I had to essentially rewrite the optimizer from scratch.

During this process, I identified some issues with the previous optimizer processors that sometimes created invalid JavaScript, and removed some processors that were too aggressive. There will be files that jxscout won't be able to optimize, but over time I'll continue solving edge cases to provide a better experience.

I also added a new processor that optimizes code like JSON.parse('{"a": "b"}' to {"a": "b"}, which is a common pattern in minified code.

July 22, 2025

CLIv1.2.1

July 22, 2025

Improved authenticated JS fetching

This release fixes several bugs that will improve jxscout's completeness:

Fixed a bug where jxscout was not downloading webpack chunks that required authentication.
Fixed a bug where jxscout was not downloading source maps that required authentication.
Fixed a bug where jxscout was not downloading application/ld+json inline scripts.

July 20, 2025

CLIv1.2.0

July 20, 2025

MCP Server release and performance improvements

This release introduces the MCP server and various performance improvements.

MCP Server

The era of hackbots is here, and jxscout is ready to help you build them. This version introduces an MCP server with 3 tools that can help you build hackbots:

get_html_routes - Allows the agent to retrieve all HTML pages tracked by jxscout for the current project.
get_js_files_loaded_by_html_file - Allows the agent to list all loaded JavaScript files for a given route. This includes discovered Webpack chunks, reversed sourcemaps, and optimized versions of the JavaScript files.
get_static_analysis_results_for_file_paths - Allows the agent to retrieve static analysis results from jxscout. This enables the agent to get discovered paths and other relevant parts of the code, so it can focus on what's important.

By default, the MCP server runs on port 3334 under the /mcp route. You can use the config command in the CLI to change the port. Here is an example configuration for Cursor:

{
              "mcpServers": {
                "jxscout": {
                  "url": "http://localhost:3334/mcp"
                }
              }
            }

This is the first version of the MCP server. I'm excited to get feedback on other tools you would like to see.

Miscellaneous Improvements

The query to get project-level descriptors was improved and should now be faster.
Descriptors are now sorted alphabetically by default.

VSCode Extensionv1.2.0

July 20, 2025

Performance and navigation improvements

This release includes some quality of life improvements to the VSCode extension.

Deprecated the toggle sort button since results are now sorted automatically by the backend.
You can now quickly navigate to specific routes of the current project by bringing up the VSCode command palette (Ctrl+Shift+P) and selecting "jxscout: Go to Route".
Project level views are now cached in memory, so you can switch between File and Project scope without waiting for the results to be loaded from the backend.

July 13, 2025

CLIv1.1.0

July 13, 2025

Improved asset discovery and navigation

This is a major release that introduces numerous important bug fixes and improvements to asset navigation in VSCode. Although there should be no breaking changes, I recommend creating a backup of your existing projects as there were some changes in how sourcemaps are saved.

To back up your projects, you can use the following commands:

$ cp -R ~/jxscout ~/jxscoutbak$ cp -R ~/.jxscout ~/.jxscoutbak

⚠️ This release has only been tested on macOS. If you are on a different OS, please let me know if you encounter any issues.

Webpack Chunk Discovery

Fixed a bug where websites that returned a 200 with HTML content for brute-forced webpack chunks caused jxscout to download those "No Content" HTML pages.

Reversed Sourcemaps

Improved how reversed sourcemaps are saved to disk. Previously, all reversed sourcemaps were saved underneath the hostname path, but this could cause conflicts between different parts of the application with available sourcemaps.
Sourcemaps are now saved in a directory relative to where they were found (e.g., https://example.com/assets/js/app.js.map will be saved to example.com/assets/js/src/...).
This change mimics how sourcemaps are reversed and shown in the "Sources" tab of Chrome.

Improved Asset Relationship Tracking

Scripts loaded with the crossorigin attribute were not being related to the loading route. This is because jxscout relied on the Referer header to determine the loading route, but with that attribute set, the Referer header is not sent.
jxscout now keeps track of scripts loaded by HTML pages and attempts to relate them to the loading route.

Improved Asset Navigation

Implemented the backend changes to support the new asset navigation updates in VSCode.
See the VSCode 1.1.0 changelog for more details.

VSCode Extensionv1.1.0

July 13, 2025

Improved asset discovery and navigation

This release includes numerous improvements to the UX for navigating assets in the VSCode extension. Please update the CLI version to 1.1.0 as well to get the latest features.

Added ability to hide descriptors

jxscout has many descriptors, and some of them might not be relevant to you. You can now hide descriptor types by right-clicking on them.

Improved asset navigation

The assets view now shows the assets in a tree structure, making it easier to navigate.

Ability to "lock" views

When changing between files, the descriptors and assets views update their results by default. You can now lock those views to prevent updating them when jumping between files.

This feature should be useful when analyzing a particular route. You can select the HTML file you want to analyze, which will make jxscout load all the assets/descriptors for that route. Then you can lock the views and analyze all the relevant code for that route.

Improved asset search

The previous version's search view was not very useful. Now search is done in memory and updates in real time, which should result in a better user experience.

You can also search for assets within the "Assets" view by bringing up the VSCode command palette (Ctrl+Shift+P) and selecting "jxscout: Go to Asset", which opens a quick pick view to search for assets.

July 6, 2025

CLIv1.0.0

July 6, 2025

Get descriptors for selected files

This is the first release of jxscout pro with a proper changelog. Going forward, every release will include detailed changelog entries to better communicate changes to users.

This release also introduces a new versioning scheme. Previously, releases were versioned using dates, but this approach doesn't work well for versioning. I've now adopted semantic versioning for better compatibility and clarity.

Versioning: Semantic Versioning

Adopted semantic versioning (major.minor.patch) with the following rules:

Major: Incremented when breaking changes are made to the communication protocol with the VSCode extension.
Minor: Incremented when new features are added.
Patch: Incremented when bugs or small improvements are made.

New Feature: Multi-file Descriptor Selection

You can now select multiple files or directories in VSCode to get descriptors for them simultaneously. This provides a more efficient workflow when analyzing multiple files.

jxscout pro CLI - multiple files selected

Improvements and Bug Fixes

Deprecated the "Filter descriptors by file path" search box in favor of the new multi-file selection feature.
Added the ability to cancel in-flight requests when switching away from the project-level descriptors view.
Duplicate descriptors are now automatically collapsed into single entries for cleaner visualization.

VSCode Extensionv1.0.0

July 6, 2025

Get descriptors for selected files

Implemented changes to support getting descriptors for selected files. See the CLI changelog for more details.