Package scanner
Bring existing projects into your dependency inventory
Scan manifests and lockfiles from repositories and CI jobs, including projects that do not restore through the proxy. Report their package inventory to your on-premises ShieldedStack deployment.
Add visibility where proxy traffic is not available
Seed the inventory from an existing repository, schedule a scan in CI, or scan a project that restores dependencies through another route. The standalone CLI reads dependency files and submits package coordinates to your ShieldedStack deployment.
Those dependencies join the workspace inventory for assessment, alerts, and SBOM exports. The scanner provides inventory; the proxy provides install-time enforcement.
Read the files your projects already produce
Coverage spans eleven package ecosystems, including Swift. Supported files include:
- JavaScript and TypeScript: npm package locks, pnpm v5/v6/v9 lockfiles, and Yarn v1 or Berry lockfiles, including development dependencies.
- .NET: NuGet lockfiles, C#, F#, and Visual Basic project references, packages.config, and Paket lockfiles.
- Python: pinned requirements, Pipenv, Poetry, and uv lockfiles.
- Java and JVM projects: Maven POM dependencies and Gradle dependency lockfiles.
- Go, Rust, Ruby, Dart, and PHP: go.mod, Cargo.lock, Gemfile.lock, pubspec.lock, and composer.lock.
- Elixir, Erlang, and Swift: mix.lock, rebar.lock, and SwiftPM Package.resolved.
The scanner parses manifests and lockfiles without running dependency resolution. Lockfiles provide exact resolved versions; unresolved ranges and unsupported dependency sources are skipped. Maven versions inherited from a parent POM or imported BOM are not resolved.
Swift coverage is scan-only. OCI image contents are assessed through the container proxy’s signed-SBOM workflow, not this scanner.
Run locally or from your existing CI jobs
Binaries are available for Linux and macOS on x64 and ARM64, plus Windows x64. Use a dry run to inspect discovered packages without uploading, then configure your proxy URL and project API key for inventory submission.
- Target the project directory. Use include and exclude patterns to select the dependency files to scan.
- Report to your deployment. Uploads go to the package proxy’s
/scansendpoint, attributed through the API key. - Repeat in CI. Schedule inventory updates or run after dependency changes. For a monorepo, scan project directories with their corresponding keys.
Exit codes report scan and upload success or failure. They are not a vulnerability-policy pass or fail result.
Get the scanner and CI setup examples →Use the inventory beyond the scan
Review findings in the console, send vulnerability and license-change alerts to your team’s channels, and query project inventory through MCP. Export the tracked dependencies as SPDX or CycloneDX when a customer or release review needs an SBOM.
Explore related capabilities
Test it on your infrastructure
Use the 30-day on-premises trial to validate your package managers, policies, and operations. Prefer a first look? The separate 7-day hosted Portal evaluation uses synthetic package activity.