Identify high-risk repositories
Obtain a list of the most at-risk source repositories based on low maintenance forecasts and high dependency counts, enabling proactive security or maintenance planning.
How it works
The agent uses the /v1/risk/top endpoint to fetch a digest of repositories with the lowest open maintenance forecasts. It filters for repositories with a significant number of dependents (e.g., >1000) to prioritize high-impact risks. The agent reviews the ranked list, noting the specific family probabilities (commits_90d, release_90d) and any open maintenance questions that are due soon, allowing the user to address critical dependencies before they fail.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
List the top 5 most at-risk repositories with at least 1000 dependents. Include their maintenance forecast probabilities and the earliest date an open maintenance question resolves.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
The weekly digest's "Most at risk this week" table as JSON: the limit repositories (1–100, default 10) with the lowest open maintenance forecasts, among source repositories of packages with at least min_dependents dependent repositoriesDeveloper docs — Anteproof