Breakage Calendar · Check a repository

Which dates hit your code?

Choose a repository folder. This page runs each date’s own search on your files and shows only the dates they touch.

Choose your repository’s top folder

or drop it here

Nothing is uploaded and nothing from your folder runs. The page reads text files up to 1 MB and skips .git, node_modules, virtual environments and build output. If your browser asks to “upload”, it is asking whether this page may read the folder.

On a phone, or for one file: paste it

The Breakage Calendar, from its first date to its last

What the page looks for

  • Runner labels and setup steps in GitHub Actions workflows
  • OpenSSL version checks and -extfile options in .github files
  • AI model names in code and configuration: OpenAI, Gemini and Claude
  • Data API addresses that are going away: USGS, Socrata and NOAA’s NAM
  • postgres image tags in Compose files and Dockerfiles
  • Homebrew formulas installed by CI or a Brewfile
  • LaunchDarkly REST calls, OpenAI prompt and eval calls
  • Scripts that read rustc’s version; XML files with a stylesheet line
  • Scheduler and test packages in package.json and Python dependency files
  • Ruby gems in Gemfile.lock
  • Android back handling in Java and Kotlin code
  • SSH libraries in dependency files and Go code: ssh2, paramiko, Go’s x/crypto/ssh and JSch

Each comes from the “How to check” step on that date. Where that step is a plain search, the page runs the same search and finds the same lines. Dates that depend on servers, certificates, clocks or browsers are listed after the result.