Deps.rs is already a useful source of truth for Rust dependency status. It would be helpful to make the same information easier for coding agents and automation to consume.
This is meant as a tracking issue for a few incremental improvements:
- Add detailed JSON status endpoints for crates and repositories. Unlike the badge-oriented
shield.json, this should expose dependency, version, and advisory details.
- Add HTML metadata, such as a
link element, that points tools to the corresponding JSON response.
- Add an
llms.txt file that briefly describes how agents and tools should use deps.rs.
The main use case is agent-assisted dependency maintenance. As a human, I can open a deps.rs page and quickly understand what needs attention. For an agent, the same information currently requires page scraping or screenshot inspection, which is more brittle than consuming a dedicated machine-readable response.
The goal is additive. This should not need to change the current human-facing pages or badge behavior.
Deps.rs is already a useful source of truth for Rust dependency status. It would be helpful to make the same information easier for coding agents and automation to consume.
This is meant as a tracking issue for a few incremental improvements:
shield.json, this should expose dependency, version, and advisory details.linkelement, that points tools to the corresponding JSON response.llms.txtfile that briefly describes how agents and tools should use deps.rs.The main use case is agent-assisted dependency maintenance. As a human, I can open a deps.rs page and quickly understand what needs attention. For an agent, the same information currently requires page scraping or screenshot inspection, which is more brittle than consuming a dedicated machine-readable response.
The goal is additive. This should not need to change the current human-facing pages or badge behavior.