Should you use it for submission planning?
CCF-Deadlines can help you collect candidate venues and keep their dates in view. Its schema combines conference identity, ranking, submission stages and timezone information. Keep the official call for papers in your submission checklist, because a catalog entry can contain both sourced facts and repository defaults.
The current README tells contributors to use 23:59:59 when an official source gives a date without a clock time, and AoE when it omits a timezone. It also tells contributors to document those defaults rather than present them as statements from the source. Before submitting, check whether the displayed time and zone came from the conference or from those conventions. A truly unpublished date remains TBD. These conventions appear in the supplied current README; the supplied README at the measured commit does not contain that guidance.
What our sandbox established
Our run on September 29, 2026, at commit eac98d7 recorded successful install and build steps, but skipped tests.
Installation took 25 seconds; the build step took 4 seconds. The harness stored exit code zero for each. It skipped tests with the reason "no script", so this review reports no passing-test count. The detector also recorded no top-level tests directory, which does not establish that the repository contains no tests elsewhere.
The empty build log tail and missing command text limit what we can conclude. The record does not establish that the website rendered, the CLI answered a query, exports contained correct deadlines, or deployment completed. The timings describe harness steps, not application performance or conference-data accuracy.
The MrKeyoor testing methodology explains how command outcomes reach reviews. The supplied October 2026 methodology page does not establish which procedure version the September run used. This correction uses the stored run and includes no new execution.
What the catalog gives a research group
The repository README documents CCF, CORE and TH-CPL ranking fields, conference links, event dates and locations. Records can distinguish abstract, submission, rebuttal and decision deadlines. Required timezone information supports UTC offsets, AoE and Pacific Time with daylight-saving adjustment.
The README links a website, tabular portal, Python CLI, iCal subscriptions and companion interfaces. Those are documented ways to access the catalog, not interfaces exercised in our sandbox. For a lab, the practical next step is to choose a few relevant venues, compare their records with official calls, and check the calendar output before relying on reminders.
Self-hosting needs a separate check
The current deployment workflow installs Python dependencies, tests share-card rendering, assembles conference data and generates calendar and RSS files. It then installs Rust nightly and the WebAssembly target and builds with Trunk.
That workflow shows why a short Python-oriented harness result is insufficient evidence for the complete site. If you plan to self-host, inspect and run the documented pipeline in your own environment, including the output you intend to serve. Our stored checkout had no detected Dockerfile or Compose file.
Historical statistics need their own verification
The supplied extract of issue 1888 shows a closed issue whose body and checkpoints describe an unfinished acceptance-rate audit. The issue's closed status does not establish complete historical verification.
The checkpoints distinguish verified annual figures from missing denominators, conflicting sources and pending decisions. An acceptance-rate gap does not establish an incorrect submission deadline. Likewise, a correct countdown does not validate the historical statistics beside it.
When a narrower tracker fits better
Hugging Face AI Deadlines focuses on top-tier AI conferences. Its README describes the project as based on Papers with Code AI Deadlines and says the upstream repository is no longer maintained. That is Hugging Face's maintenance assessment, not a maintenance audit from our run. Consider it when your venue list is confined to AI; our sandbox did not test it or compare deadline accuracy.
SecDeadlines covers security and privacy deadlines, with inclusion criteria for academic conferences and workshops. Its criteria ask about a call for papers, submissions, review and proceedings. Consider it for specialist venue planning or alongside CCF-Deadlines when checking relevant listings. The supplied evidence does not establish that either catalog has more complete coverage.
How to read the scores
The editorial rubric runs from 1 to 5: 1 means substantial evidenced obstacles, 2 means significant limitations, 3 means useful with material qualifications, 4 means strong supporting evidence with a stated limitation, and 5 requires broad evidence with few material gaps. An unassessed dimension receives no numerical score. These are editorial judgments, not benchmarks or security ratings.
Complete setup ease is unassessed. The successful recorded installation establishes an installation outcome, but the unidentified build step and absence of application validation cannot support a rating for complete setup.
Documentation receives 4 for the explicit schema, contribution process and current deployment workflow, with end-to-end validation still absent. Community receives 4 for the documented contribution process and detailed collaborative audit checkpoints; this assesses visible contribution work, not adoption, response speed or queue size. Maturity receives 3 for the documented catalog and outputs, qualified by incomplete historical verification in the supplied audit record and limited application testing.

