Add client data updates, last modification date script, and data about clients' last modification dates#2018
Merged
bdaehlie merged 10 commits intoletsencrypt:mainfrom Aug 27, 2025
Merged
Conversation
This commit manually adds all pending client data PRs from the Let's Encrypt website repository, in a few cases also manually editing the comment fields.
This commit adds data from a run of my Python script to collect the last modification time of each project that has a readily identifiable git URL. This data can be used for various purposes, most importantly hiding clients on the Let's Encrypt web site that appear not to be actively maintained. It's stored in Unix time format as a numeric field called "last_commit". Note that not all projects get annotated this way, because not all of them have a git repository page (or one that can be determined from the existing data). A jq command line to view the clients with this field by their last commit is jq -r '."list"[] | select(."last_commit")? | "\(now - .last_commit | round): \(.name)" ' < clients.json I'll separately commit the Python script itself somewhere so that it can be rerun in the future to update this information.
This script automatically updates data in data/clients.json by cloning referenced git repositories and noting the dates of their last commits.
This was referenced Aug 27, 2025
Closed
Closed
bdaehlie
approved these changes
Aug 27, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This PR includes commits to manually incorporate data from all pending client PRs (those tagged as client-options, at https://github.com/letsencrypt/website/pulls?q=is%3Apr+is%3Aopen+label%3Aclient-options).
It also includes a new Python script to add the last commit date to each client based its detected git repository URL, if any. That script has been run once, and the results are also included in the PR.
This data can be used to split out clients that are no longer being maintained into a separate JSON file, or to hide them on the Let's Encrypt site.
I added an additional script that uses the data to entirely remove such clients from the JSON file.