mrkeyoor.comAsk

ccfddl/ccf-deadlinestested 29 Sept 2026commit eac98d7

ccf-deadlines review

Use CCF-Deadlines as a conference-planning catalog if its ranking fields fit your research.

  • Build 4 s
25 sto install
  • 65 packages
Dataevaluationupdated 01 Nov 2026
+22stars / 7d

Use CCF-Deadlines to find computer science conference deadlines and plan reminders, then confirm submission details on the conference's own site. It is a collaborative catalog with conference YAML records, ranking fields and several interfaces. Our run on September 29, 2026, at commit eac98d7 recorded successful install and build steps, but skipped tests.

Verdict

Use CCF-Deadlines as a conference-planning catalog if its ranking fields fit your research. Our sandbox recorded installation in 25 seconds and a build step in 4 seconds, with tests skipped. Complete setup ease remains unassessed, and the run did not establish a working deployment or correct conference records. Check official calls before submitting, and validate the calendar or interface you intend to use.

We ran it

Lab card: what happened when we ran ccf-deadlines
Lab card from our sandbox run
Screenshot of ccf-deadlines (ccfddl.com)
ccfddl.com
Install✓ · 25s65 packages · 179 MB
Build✓ · 4s
Testsn/ano test script
Known vulns0(pip-audit)
Repo632 files~13,350 lines of source · 10.4 MB · 3 CI workflows

Answers from our run

Does ccf-deadlines build from source?

Dependencies installed in 25 seconds (65 packages), and the build succeeded in 4 seconds. We cloned commit eac98d7 into a clean Debian container with 3 CPUs and no project-specific setup.

Does ccf-deadlines have tests you can run?

Not through a standard command: the project exposes no test script or target that our harness could run.

Does ccf-deadlines have known vulnerabilities in its dependencies?

pip-audit found none in the dependency tree at the time of our run.

Who should not use ccf-deadlines?

Researchers who need the countdown alone to establish an official submission time or timezone.

What are the alternatives to ccf-deadlines?

Hugging Face AI Deadlines, SecDeadlines. Use CCF-Deadlines as a conference-planning catalog if its ranking fields fit your research.

Setup4/5Our source checkout installed in 25 s and built in 4 s with 65 dependencies, but we did not run a README task.Editor’s note: Complete setup ease is unassessed: installation succeeded, but the build command is absent and the record does not establish a working application, calendar export, CLI or deployment.
Docs4/5The supplied README specifies required fields, timezone handling and contribution steps; the current workflow documents deployment stages. This supports a documentation rating under the visible rubric, while our run did not verify the instructions end to end.
Community4/5The documented contribution process and detailed multi-conference audit checkpoints support this assessment of visible collaborative work. The rating does not measure adoption, review speed, queue size or general community health.
Maturity3/5The documented schema and outputs support a qualified assessment of practical usefulness. Historical verification remains incomplete in the supplied audit record, and our sandbox did not validate application behavior or data accuracy.

How we score

Who it’s for

Researchers who organize conference choices around CCF, CORE or TH-CPL rankings.
Labs that want a shared conference catalog and calendar subscriptions.
Contributors willing to check official conference information before proposing YAML changes.
Maintainers prepared to inspect the Python data pipeline and Rust browser build before self-hosting.

Who it’s NOT for

Researchers who need the countdown alone to establish an official submission time or timezone.
Teams requiring a tested production deployment or CLI workload from our sandbox record.
Readers seeking evidence that every conference deadline or historical acceptance figure has been verified.
Maintainers who need a documented container deployment in the recorded checkout: our detector found no Dockerfile or Compose file.

Setup reality

Our run on September 29, 2026, used commit eac98d7, whose full SHA is eac98d73b7ed1f17834c949f9a5ddacc3fbc8d9b. In our Python 3.12 Debian Bookworm sandbox with 3 CPUs and 8 GB of memory, installation took 25 seconds and the recorded build step took 4 seconds. Both returned exit code zero without timing out. The stored dependency footprint was 65 packages and 179 MB.

The build tail is empty and the record does not identify the build command. It therefore cannot establish that Trunk, the browser application, calendar generation, the CLI or production deployment worked. Tests were skipped with the recorded reason "no script"; there is no passing-test count. Complete setup ease remains unassessed.

Pip-audit recorded zero advisories. Scan coverage is unknown because the supplied record has no scannedPackages value; its packages field is zero. This does not establish that all dependencies were scanned or that the repository is secure.

The current deployment workflow separately documents Python data assembly, iCal and RSS generation, share-card tests, Rust nightly, the WebAssembly target and Trunk. Those current instructions are not a log of our September run.

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.

Alternatives

ProjectWhat it isPick it when
Hugging Face AI DeadlinesA deadline web app focused on top-tier AI conferences.Consider it when your venue list is confined to AI and you want to evaluate a narrower tracker. Its README says it is based on Papers with Code AI Deadlines; our sandbox did not test its accuracy or deployment.
SecDeadlinesA security and privacy deadline tracker with stated academic conference and workshop inclusion criteria.Consider it for specialist security, privacy or cryptography venue planning, or alongside CCF-Deadlines when checking relevant listings. The supplied evidence does not establish comparative completeness.

What people are saying

  1. [github-trending] ccfddl/ccf-deadlines

Sources

  1. CCF-Deadlines repository
  2. CCF-Deadlines deployment workflow
  3. Issue 1888: acceptance-rate backfill
  4. Issue 239: automatically update conference times
  5. Issue 2485: Chrome extension sometimes not working

More data reviews