> For the complete documentation index, see [llms.txt](https://docs.stepsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stepsecurity.io/developer-machines/packages.md). # Packages The **Packages** section of Dev Machine Guard gives you visibility into the open-source packages, system packages, and package-manager configuration present on your developer machines. The [Packages](/packages/oss-package-search.md) product area enforces controls at install time through Secure Registry. This section covers inventory and posture on the endpoints themselves: what is installed across your fleet, and how each machine's package managers are configured. Together they answer "what is on my developer machines, and are those machines set up to pull packages safely?" This section contains three pages: * **OSS Packages**: an inventory of the open-source packages installed on developer machines across JavaScript, Python, Go, Rust, PHP, .NET, Ruby, Conda, Java, Swift, and Homebrew. Use **Advanced search** to find where a specific package and version is installed across your fleet when a compromised package is disclosed. * **System Packages**: an inventory of OS-level packages installed through system package managers (Homebrew on macOS, `dnf` / `apt` and others on Linux), with version distribution, signature status, and per-device spread. * **Package Configs**: an audit of package-manager configuration on each device across JavaScript, Python, Go, Rust, PHP, .NET, Ruby, Conda, Java, and Swift, showing the effective registry, whether a release-age cooldown is in effect, and the credentials configured. --- # 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.stepsecurity.io/developer-machines/packages.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.