OSS Package Search

Available for Enterprise Tier Only

OSS Package Search lets you quickly identify where specific open-source packages appear across your organization, from pull requests and repositories to developer machines. When a package is found to be compromised or vulnerable, you can use this feature to understand your blast radius and take targeted remediation steps.

You can search at the organization level or across your entire tenant, depending on your scope of access.

Supported ecosystems

OSS Package Search supports the following package ecosystems:

• npm: the Node.js package registry
• PyPI: the Python Package Index
• Maven: the Java package ecosystem (Maven Central)
• NuGet: the .NET package ecosystem (nuget.org)

Select the ecosystem from the Package ecosystem toggle at the top of the search form.

Search Scope

OSS Package Search covers two surfaces:

• CI/CD and Repositories: identifies where a package was introduced across pull requests and default branches. Results link directly to the PR where the dependency was added, so you can revert or patch it quickly.
• Developer Machines: identifies where a package is installed on developer endpoints, including packages installed by AI coding agents and tools. For each match, the search returns the exact file path and package manager used, which you can use to build an MDM or EDR remediation script and verify removal after cleanup.

Supported Files

OSS Package Search inspects the following dependency and lock files when indexing packages from CI/CD pipelines, repositories, and developer machines.

npm ecosystem

Package manager	Files
npm	package-lock.json
Yarn	yarn.lock
pnpm	pnpm-lock.yaml, pnpm-lock.yml
Bun	bun.lock

PyPI ecosystem

Package manager	Files
pip	requirements*.txt, requirements*.in, files inside a requirements/ directory, setup.py, setup.cfg
Poetry	poetry.lock
uv	uv.lock
Pipenv	Pipfile.lock
Conda	environment.yml, environment.yaml
PyLock	pylock.toml, pylock.<name>.toml

Maven ecosystem

Package manager	Files
Maven	pom.xml, *.pom
Gradle (lock file)	gradle.lockfile, buildscript-gradle.lockfile
Gradle (verification metadata)	gradle/verification-metadata.xml
Bazel (Maven rules)	BUILD.bazel, MODULE.bazel, WORKSPACE

NuGet ecosystem

Package manager	Files
NuGet (PackageReference)	*.csproj, *.vbproj, *.fsproj
NuGet (legacy)	packages.config
NuGet (lock file)	packages.lock.json
NuGet (Central Package Management)	Directory.Packages.props, Directory.Build.props
.NET build output	*.deps.json

Only packages.lock.json records transitive dependencies. The other files list direct dependencies as declared, so a search that relies on them alone will not surface a package that reaches your project indirectly. Enable NuGet lock files if you need transitive coverage.

How to Use OSS Package Search

Step 1: Navigate to StepSecurity Dashboard → OSS Package Search

Step 2: Configure your search filters

• Search Scope: choose Organization Search to search within your current organization, or Tenant Search to search across all organizations in your tenant.
• Package ecosystem: choose npm, PyPI, Maven, or NuGet.
• Search Type: choose Custom Search to specify packages manually, or a compromised packages search such as Compromised Packages (Exact Versions) to check your organization against known compromised packages.
• Repository: optionally narrow results to a specific repository.
• Seen In: filter by where the package was detected. Options include All (PRs, Default Branch & Dev Machines), or a specific surface.
• Time Range: optionally select a date range to limit results.

When you choose a compromised packages search, Packages included in this search shows how many packages and versions the search covers. Select View all to see the full list.

Step 3: Add the packages you want to search for.

Enter a package name and, if applicable, one or more specific versions. Click Add Package to add more packages to the same search. Results can be exported as CSV.

Step 4: Run the search

Click Search. A search can take one to two minutes to finish.

While the search runs:

• The Search button changes to Stop. Hover over Stop to see how far the search has progressed, or click it to end the search early.
• Results appear as they are found, so you can start reviewing them before the search finishes.
• Each results section shows Searching for matching results until it has results to display. You can collapse a section while the search continues.

Step 5: Review the results

The results header shows how many results were found. Results are grouped into two collapsible sections, each with its own search box for narrowing the loaded results:

• PRs and Default Branch: each finding shows the pull request title and number, the repository, the author, the file the package was detected in (for example package-lock.json), and when it was last updated. The matching package version appears below the finding. Click View PR to open the pull request.

• Dev Machines: each device shows its hostname, user, and platform, followed by a table of matching packages with First Seen, Last Seen, Project Path, and Status. Select View all below the table to see every matching package on that device.

Use the Package Status filter in the results header to narrow the results by status, and Export received results to download the results received so far.

Follow this interactive demo to see how this works:

For a complete guide to preventing, detecting, and responding to package attacks, see OSS Supply Chain Security