> 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/software-supply-chain-security/risk-and-remediation/malicious-packages/pull-request-workflow.md). # Pull request workflow #### Shift-left context Pull request feedback blocks a malicious package before it reaches CI, deployment, and runtime. This is the primary shift-left enforcement point for teams without the IDE extension. #### Receive malicious package feedback in a pull request When a pull request introduces or newly references a malicious package, the PR scan detects it and adds a comment. The comment presents the finding with the package name and version, the Malware ID linked to its OSV advisory, the CRITICAL severity, and the advisory summary, together with the required action to remove the package. The comment body is assembled from the finding data, so the exact wording follows the malicious package finding summary and description. If the governing policy is configured to block, the pull request status is set to fail. --- # 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/software-supply-chain-security/risk-and-remediation/malicious-packages/pull-request-workflow.md?ask=&goal= ``` `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.