{"meta":{"title":"Puntos de conexión de la API de REST para la revisión de dependencias","intro":"Usa la API de REST para interactuar con los cambios de dependencia.","product":"REST API","breadcrumbs":[{"href":"/es/rest","title":"REST API"},{"href":"/es/rest/dependency-graph","title":"Gráfica de dependencias"},{"href":"/es/rest/dependency-graph/dependency-review","title":"Revisión de dependencias"}],"documentType":"article"},"body":"# Puntos de conexión de la API de REST para la revisión de dependencias\n\nUsa la API de REST para interactuar con los cambios de dependencia.\n\n## Acerca de la revisión de dependencias\n\nPuedes usar la API de REST para ver los cambios de dependencia y el impacto de estos cambios en la seguridad antes de agregarlos a tu entorno. Puede ver la diferencia de dependencias entre dos confirmaciones de un repositorio, incluidos los datos de vulnerabilidad de las actualizaciones de versiones con vulnerabilidades conocidas. Para más información sobre la revisión de dependencias, consulta [Revisión de dependencias](/es/code-security/concepts/supply-chain-security/dependency-review).\n\n> \\[!NOTE]\n> Most endpoints use `Authorization: Bearer <YOUR-TOKEN>` and `Accept: application/vnd.github+json` headers, plus `X-GitHub-Api-Version: 2026-03-10`. Curl examples below omit these standard headers for brevity.\n\n## Get a diff of the dependencies between commits\n\n```\nGET /repos/{owner}/{repo}/dependency-graph/compare/{basehead}\n```\n\nGets the diff of the dependency changes between two commits of a repository, based on the changes to the dependency manifests made in those commits.\n\n### Parameters\n\n#### Headers\n\n* **`accept`** (string)\n  Setting to `application/vnd.github+json` is recommended.\n\n#### Path and query parameters\n\n* **`owner`** (string) (required)\n  The account owner of the repository. The name is not case sensitive.\n\n* **`repo`** (string) (required)\n  The name of the repository without the .git extension. The name is not case sensitive.\n\n* **`basehead`** (string) (required)\n  The base and head Git revisions to compare. The Git revisions will be resolved to commit SHAs. Named revisions will be resolved to their corresponding HEAD commits, and an appropriate merge base will be determined. This parameter expects the format {base}...{head}.\n\n* **`name`** (string)\n  The full path, relative to the repository root, of the dependency manifest file.\n\n### HTTP response status codes\n\n* **200** - OK\n\n* **400** - Bad Request\n\n* **403** - Response for a private repository when GitHub Advanced Security is not enabled, or if used against a fork\n\n* **404** - Resource not found\n\n* **500** - Internal Error\n\n* **503** - Service unavailable\n\n### Code examples\n\n#### Example\n\n**Request:**\n\n```curl\ncurl -L \\\n  -X GET \\\n  https://api.github.com/repos/OWNER/REPO/dependency-graph/compare/BASEHEAD\n```\n\n**Response schema (Status: 200):**\n\nArray of objects:\n\n* `change_type`: required, string, enum: `added`, `removed`\n* `manifest`: required, string\n* `ecosystem`: required, string\n* `name`: required, string\n* `version`: required, string\n* `package_url`: required, string or null\n* `license`: required, string or null\n* `source_repository_url`: required, string or null\n* `vulnerabilities`: required, array of objects:\n  * `severity`: required, string\n  * `advisory_ghsa_id`: required, string\n  * `advisory_summary`: required, string\n  * `advisory_url`: required, string\n* `scope`: required, string, enum: `unknown`, `runtime`, `development`"}