Review deprecation candidates

What a candidate means#

Deprecation candidates collects endpoints for evidence review. The status and reason summarize what is known about static callers and runtime coverage. A candidate is a starting point for investigation.

With runtime usage unknown, candidates remain in states such as flagged or building confidence. The page also has filters for rare caller and strong candidate, but these can be empty with the available evidence.

Record an evidence review#

1. 1

   Find the endpoint

   Search candidate paths or reasons, or filter by status. Review its static caller count and runtime label.

2. 2

   Open Review evidence

   Read the candidate reason and follow the provider and available caller source references.

3. 3

   Verify outside the index

   Check relevant traffic, consumers outside the selected repositories, externally maintained clients, and team migration obligations before planning a removal.

4. 4

   Mark reviewed for this snapshot

   An owner or admin with a verified email can record the review using Mark reviewed for this snapshot. Wait for server confirmation.

5. 5

   Revisit changed evidence

   A later snapshot can show Previous snapshot — review updated evidence. Reopen the evidence and record a fresh review when appropriate. Use Mark needs review to remove the current acknowledgment.

Plan a removal#

• Confirm which consumers and deployment environments are outside the indexed scope.
• Agree on a migration window and ownership with affected teams.
• Keep API contracts consistent with the proposed implementation change.
• Review the removal PR's report and all coverage gaps.
• Use your established production observation and rollback procedures.