> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/gold-open-source-gos/gold-packages/integrating-lineaje-gos-artifactory-proxy-into-your-ci-cd-pipeline.md).

# Integrating Lineaje GOS Artifactory Proxy into Your CI/CD Pipeline

When a build tool (Maven, pip, npm) resolves a dependency, it issues an HTTP GET request to the configured registry URL. With the Lineaje GOS Artifactory Proxy enabled, that URL resolves to the Proxy endpoint instead of the upstream public registry. The following sequence describes what happens for every artifact request: 

1. **Build tool issues HTTP GET**

   The build tool requests an artifact using the standard package-manager protocol (Maven repository layout, PyPI simple API, or npm registry API). The only difference from a vanilla build is that the registry hostname points to the Proxy. 
2. **Authentication check**

   The proxy validates the provided credentials (Basic Auth over HTTPS). Requests without valid credentials receive HTTP 401 immediately. 
3. **Package coordinate extraction**

   The Proxy parses the request path to extract the package's PURL (Package URL) coordinates — ecosystem, name, and version. 
4. **GOS & policy evaluation**

   The extracted PURL is evaluated against the Gold Open Source index and your organization's custom policies. Results are cached to ensure build performance is not impacted. 
5. **Allow or block decision**

   In enforce mode, non-gold packages receive an error response. To learn more, see [HTTP Response Codes](/gold-open-source-gos/gold-packages/integrating-lineaje-gos-artifactory-proxy-into-your-ci-cd-pipeline/http-response-codes.md). In observe mode, all packages are forwarded regardless of status. 
6. **Telemetry & audit**

   The outcome (allowed / blocked / policy-violated) is recorded on the Lineaje platform with full provenance detail. Policy violation messages are also injected into the HTTP response and appear in build logs. 


---

# 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://docs.veedna.com/gold-open-source-gos/gold-packages/integrating-lineaje-gos-artifactory-proxy-into-your-ci-cd-pipeline.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.