The shared deadline data is the reason to use it
Each record can hold 3 ranking systems, multiple deadline stages, and a precise timezone. CCF-Deadlines puts those fields into one catalog, then publishes them as countdowns, tables, iCal files, RSS feeds, and command-line output. The repository is most useful as a common source for a research group, with the website acting as one view over the data.
A conference record also carries a short name, subject code, DBLP identifier, event date, and location. A deadline may include abstract, rebuttal, and decision dates as well as submission time. Rankings can cover CCF, CORE, and TH-CPL. That is enough structure to answer a practical question such as which A-ranked AI venues close next month.
Ten subject codes define the catalog's center of gravity
The schema divides venues among 10 CCF subject codes, including AI, databases, security, software engineering, graphics, and theory. Non-CCF entries can use an N rank, and optional ranking fields widen the lens. Still, the organizing system comes from computer science conference lists. It is a poor fit for journals, grant calls, workshops outside the catalog, or a field that does not use these ranking systems.
The README makes contribution straightforward: edit a conference YAML file and open a pull request. Required fields force contributors to specify the timezone and exact deadline format instead of leaving readers to interpret a date. The format supports UTC offsets, Anywhere on Earth, and Pacific Time with daylight-saving adjustment. That precision is useful, provided the source date itself is current.
What happened when we ran it
Our sandbox installed commit eac98d7 in 25 seconds, pulling 65 packages and using 179 MB on disk. The build passed in 4 seconds. This ran inside an unprivileged Debian container with 3 CPUs, 8 GB of RAM, Python 3.12, and no secrets. Pip-audit found 0 known vulnerabilities.
The harness did not find a tests script or target, so it skipped tests. That is not a passing suite. The repository signals also showed no top-level tests directory, though its workflow and subdirectories contain their own check commands. We report the path our sandbox executed: dependency installation and build worked, while no test result was produced.
The checkout was modest at 10.4 MB, 632 files, and about 13,350 lines of source. Its deployment path has more moving parts than those numbers suggest. Python assembles YAML into JSON and creates iCal and RSS output. The browser front end uses Rust, WebAssembly, and Trunk. GitHub Actions installs Rust nightly and the WebAssembly target after the Python stage.
Calendars and the CLI make the catalog reusable
The Python CLI filters on 3 axes, conference, subject, and rank, and can return JSON. Generated iCal and RSS files put dates into tools researchers already check. The README also points to a WeChat applet, Raycast extension, SwiftBar plugin, Chrome extension, and a separate terminal interface.
Those options remove the need to scrape the visual site. A lab can subscribe to a calendar, query JSON in a script, or keep a filtered terminal view. Generated data is split so the front end can load current deadlines before historical records. If a split file is missing during deployment, the documented loader falls back to the original full JSON file.
A 248-pull-request queue slows human review
GitHub showed 9,388 stars, 8 open issues, and 248 open pull requests on September 30, 2026. The repository was pushed that same day. Many recent proposals add or correct acceptance statistics, while issue 1888 says the 2021 through 2026 backfill remains in progress and that an open pull request does not mean a conference has been fully checked.
That is active work, but the queue is also review debt. A date or acceptance figure can sit outside the main branch while maintainers inspect its evidence. Open issue 239 raises the older problem directly: conferences that attract little attention may go without updates. Community maintenance spreads the workload; it does not guarantee equal coverage.
Final submission dates still belong to the conference
Our 4-second build says nothing about whether tomorrow's submission date is correct. Check the linked conference site for the current call, timezone, track, and extension, then use CCF-Deadlines for reminders. Issue 2485, which reports an unreliable extension popup in Edge, is another reason to keep a calendar export or the main site available.
The trade is fair for most computer science labs. The data format is readable, and the outputs cover browsers, calendars, feeds, and terminals. Adopt it as shared plumbing if its rankings match your field. Keep the official conference page in the submission checklist, because a missed deadline costs far more than one extra verification.