Analyze package manifest

Parse a package manifest and return dependency information with documentation URL mappings. This is a preview - no subscriptions are created.

POST /dependencies/analyze

Analyze package manifest

cURL

curl --request POST \
  --url https://apigcp.trynia.ai/v2/dependencies/analyze \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "manifest_content": "<string>",
  "manifest_type": "package.json",
  "filename": "<string>"
}
'

200

{
  "manifest_type": "<string>",
  "total_dependencies": 123,
  "dependencies": [
    {
      "name": "<string>",
      "version": "<string>",
      "registry": "<string>",
      "is_dev": true
    }
  ],
  "mappings": [
    {
      "name": "<string>",
      "registry": "<string>",
      "docs_url": "<string>",
      "mapping_source": "<string>",
      "confidence": 123
    }
  ],
  "unmapped_count": 123,
  "unmapped_packages": [
    "<string>"
  ]
}

Authorizations

Authorization · string · header · required

API key must be provided in the Authorization header

Body

application/json

manifest_content · string · required

Raw content of the manifest file

manifest_type · enum<string> | null

Manifest type. Auto-detected if not provided.

Available options: package.json, requirements.txt, pyproject.toml, Cargo.toml, go.mod, Gemfile

filename · string | null

Original filename for type detection

Response

200

application/json

Successful Response

manifest_type · string · required

total_dependencies · integer · required

dependencies · DependencyItem · object[] · required

Show child attributes

mappings · MappingItem · object[] · required

Show child attributes

unmapped_count · integer · required

unmapped_packages · string[] · required