Skip to main content
POST
/
v2
/
geoprovenance
/
origin
/
components
Get component-level Geo Provenance based on contributor origin commit times This is the current method that accepts ComponentsRequest for enhanced component identification Replaces the deprecated GetComponentOrigin method
curl --request POST \
  --url https://api.example.com/v2/geoprovenance/origin/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_locations": [
    {
      "purl": "pkg:github/scanoss/engine@5.0.0",
      "locations": [
        {
          "name": "ES",
          "percentage": 65.5
        },
        {
          "name": "DE",
          "percentage": 20.3
        },
        {
          "name": "US",
          "percentage": 14.2
        }
      ]
    }
  ],
  "status": {
    "status": "SUCCESS",
    "message": "Geo-provenance origin successfully retrieved"
  }
}

Body

application/json

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.

​
components
Array of component requests to analyze · object[]
required

Response

A successful response.

Component level Origin Response data (JSON payload) Contains geo-provenance information based on contributor origin commit times. This is the current response format that replaces the deprecated OriginResponse. Provides enhanced component identification and location data.

​
components_locations
Information about a component and its geographic origins · object[]
​
status
object

Detailed response details.