# Uploading Scan Results The best way to let the Seal platform track your vulnerabilities is by [integrating your source control](/fundamentals/readme/package-discovery.md) with the Seal app. However, this isn't always possible. An alternative way of letting Seal track your vulnerabilities is by using the Seal CLI run as part of your CI pipeline, and having it report home to the Seal server the vulnerable packages you're using. This is slightly less reliable than a direct source control integration, but can still provide an accurate picture of the vulnerabilities in your project. If you're only using the CLI for scanning then just append the `--upload-scan-results` flag to the `seal scan` command. If you're using the CLI to fix the vulnerabilities, either through [Automatic Remediation](/fundamentals/deployments/automatic-remediation.md), the [Remote Configuration](/fundamentals/deployments/remote-configuration.md) or the [Local Configuration](/fundamentals/deployments/local-configuration.md) deployments, then just append the `--upload-scan-results` flag to the `seal fix` command. --- # Agent Instructions: 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: ``` GET https://docs.sealsecurity.io/fundamentals/cli/uploading-scan-results.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.