Skip to main content
This guide walks through the two-step workflow for checking whether an open-source package is malicious and retrieving detailed threat intelligence. It’s useful for integrating into your SOAR or security tooling to automatically check resources and trigger downstream blocking or alerting when a match is found.
Subscription Required: This uses a paid endpoint available to Researcher Pro and Enterprise users.
1

Check if a resource is malicious

Use the check-malicious endpoint to query OpenSourceMalware for a specific package.

Response — malicious package found

Response — clean package

2

Interpret the response

Use this logic to decide your next step based on the response:
What counts as “recent” depends on your risk tolerance. For most teams, a scan within the last 7 days is sufficient. For high-security environments, you may want scans within 24 hours.
3

Retrieve full threat intelligence

When check-malicious returns malicious: true, use the threat_id from the response to pull the full threat description and associated IOCs. This step requires a Pro or Enterprise API key.
This workflow also works for other resource types:

Repository

Domain

URL

Container

1

Full example script

This JavaScript example puts both steps together into a single reusable function.