How Thirdpass Works
Thirdpass separates ecosystem-specific package handling from review coordination, so coverage gathered for one package artifact can be reused by every project that depends on it.
Ecosystem extensions find dependency files, understand registry metadata, and fetch exact package archives by version.
The server keeps a prioritized queue of package versions. Nightshift mode keeps asking for the next target in a loop.
Each review focuses on selected files, while the configured review agent can use the rest of the package as context.
The check command asks extensions to identify dependencies, then compares them with submitted and committed project reviews.