utils:dependency-scanner

To scan plugins for required dependencies, run the scanner against your plugin directory to read plugin files, resolve references, and group dependencies by source. It outputs a JSON report detailing all required dependencies and tool references.

Checking plugin dependencies for a marketplace audit involves scanning all enabled marketplace plugins to surface duplicate dependencies or conflicts. The scanner compares dependencies across plugins and produces a JSON summary to guide safe updates.

Yes, you can use dependency scanning for CI validation of plugin code. The scanner reads plugin files and resolves references to identify required system tools and skills, outputting a JSON report that can be evaluated in your continuous integration pipeline.

Pattern matching resolves references in plugin files by reading the code, identifying required dependencies and tool references, and grouping them by source. This mechanism detects coupling and risk across all enabled plugins or a specific targeted plugin.

Yes, you need Python to run a plugin dependency scan. The scanner is executed as a Python script, reading your plugin directory and generating a JSON summary of required dependencies, skills, and system tools.

A limitation when scanning a specific plugin for dependencies is that the scanner strictly reads plugin files and resolves references to output a JSON report. It identifies system-tool and plugin dependencies but does not modify the code or automatically resolve version conflicts.