Join us in London for Infosecurity Europe June 2 – 4, 2026 | Booth C69 | Excel London | Get a FREE ticket
curl --request POST \
--url http://api.scanoss.com/v2/vulnerabilities/cpes/components \
--header 'Content-Type: application/json' \
--data '
{
"components": [
{
"purl": "pkg:github/scanoss/engine@1.0.0"
},
{
"purl": "pkg:github/scanoss/scanoss.py@v1.30.0"
}
]
}
'{
"components": [
{
"purl": "pkg:github/scanoss/engine",
"requirement": "1.0.0",
"version": "1.0.0",
"cpes": [
"cpe:2.3:a:scanoss:engine:1.0.0:*:*:*:*:*:*:*"
]
},
{
"purl": "pkg:github/scanoss/scanoss.py@v1.30.0",
"requirement": "",
"version": "v1.30.0",
"cpes": [
"cpe:2.3:a:scanoss:scanoss.py:1.30.0:*:*:*:*:*:*:*"
]
}
],
"status": {
"status": "SUCCESS",
"message": "CPEs Successfully retrieved"
}
}Returns Common Platform Enumeration identifiers for multiple components in a single request. CPEs are used to identify IT platforms in vulnerability databases and enable vulnerability scanning and assessment.
curl --request POST \
--url http://api.scanoss.com/v2/vulnerabilities/cpes/components \
--header 'Content-Type: application/json' \
--data '
{
"components": [
{
"purl": "pkg:github/scanoss/engine@1.0.0"
},
{
"purl": "pkg:github/scanoss/scanoss.py@v1.30.0"
}
]
}
'{
"components": [
{
"purl": "pkg:github/scanoss/engine",
"requirement": "1.0.0",
"version": "1.0.0",
"cpes": [
"cpe:2.3:a:scanoss:engine:1.0.0:*:*:*:*:*:*:*"
]
},
{
"purl": "pkg:github/scanoss/scanoss.py@v1.30.0",
"requirement": "",
"version": "v1.30.0",
"cpes": [
"cpe:2.3:a:scanoss:scanoss.py:1.30.0:*:*:*:*:*:*:*"
]
}
],
"status": {
"status": "SUCCESS",
"message": "CPEs Successfully retrieved"
}
}Documentation Index
Fetch the complete documentation index at: https://docs.scanoss.com/llms.txt
Use this file to discover all available pages before exploring further.
Represents a list of software component to be analyzed by SCANOSS API services. Allows analysis of multiple software components in a single API call, improving performance over individual requests.
Represents a list of software component to be analyzed by SCANOSS API services. Allows analysis of multiple software components in a single API call, improving performance over individual requests.
Show child attributes
A successful response.
Success example. For error cases, each component block reports the processing status via info_message and info_code. Example: {"components":[{"purl":"pkg:github/scanoss/engine","requirement":"1.0.0","version":"1.0.0","cpes":["cpe:2.3:a:scanoss:engine:1.0.0:::::::*"]},{"purl":"pkg:github/unknown/component","requirement":"","version":"","cpes":[],"info_message":"Component not found in database","info_code":"COMPONENT_NOT_FOUND"}],"status":{"status":"SUCCESS","message":"Request processed"}}