> For the complete documentation index, see [llms.txt](https://docs.safetycli.com/safety-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.safetycli.com/safety-docs/pyup.io-is-now-safety-cybersecurity.md).
# PyUp.io is now Safety Cybersecurity
PyUp.io rebranded to Safety in July 2023.
Over the past five years, thousands of teams have secured their open-source Python projects thanks to PyUp’s industry-leading vulnerability database and Safety CLI scanner.
As Safety Cybersecurity, we will be expanding these capabilities by focusing on reducing vulnerability noise, securing your systems end-to-end, and applying the same industry-leading data analysis and features to the Javascript, Java, .NET, Go, Rust, C and Ruby ecosystems.
New Safety Cybersecurity Logo
**What does this mean for existing customers?**
1\. Invoices, contracts, and other formal documentation, including [Terms of Service](https://campaigns-events.pdx-1.onpdr.com/track/link/g034rj38y9/9g6goys8e3obuyj1klfueek0f/n4g034y9q6), will now be issued from Safety CLI Cybersecurity, Inc.
2\. There are no changes to ownership structure.
3\. Our public website will transition from [https://pyup.io](https://campaigns-events.pdx-1.onpdr.com/track/link/g034rj38y9/9g6goys8e3obuyj1klfueek0f/ry10ejndo7) to [https://safetycli.com](https://campaigns-events.pdx-1.onpdr.com/track/link/g034rj38y9/9g6goys8e3obuyj1klfueek0f/v5p0obrdrw).
4\. All existing features will continue to work as they do today.
[Read about our rebrand from PyUp to Safety Cybersecurity, improvements to the Safety CLI vulnerability scanner, and more here.](https://safetycli.com/research/welcome-to-safety)
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.safetycli.com/safety-docs/pyup.io-is-now-safety-cybersecurity.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
