> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/application-security/code-security/code-security-scanners/malicious-packages/api-workflow.md).

# API Workflow

#### When to use the API

Use the public API to check packages for malicious status from external consumers and automation, for example, to evaluate a dependency set outside the tenant.\
NOTE: The Cortex CLI consumes these same public endpoints because it runs outside the Kubernetes cluster and cannot reach the internal endpoints.

#### Supported operations

| Operation                     | Method | Endpoint                                        | Description                                                                                                                            |
| ----------------------------- | ------ | ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Check packages (boolean)      | POST   | `public_api/appsec/v1/packages/malicious`       | Returns, for each submitted package, whether it is malicious.                                                                          |
| Query packages (full details) | POST   | `public_api/appsec/v1/packages/malicious/query` | Returns full malicious package details — Malware ID, affected versions, summary, and advisory link — for confirmed malicious packages. |

For detailed information on Malicious Package APIs, refer to [Cortex API Overview](https://cortex-docs.paloaltonetworks.com/cortex-api-overview/).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/application-security/code-security/code-security-scanners/malicious-packages/api-workflow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.