Journal of Statistical Software Submission Guide
A practical Journal of Statistical Software submission guide for statistical-software authors evaluating code, paper, reproducibility, and journal fit before upload.
Readiness scan
Find out if this manuscript is ready to submit.
Run the Free Readiness Scan before you submit. Catch the issues editors reject on first read.
How to approach Journal Of Statistical Software
Use the submission guide like a working checklist. The goal is to make fit, package completeness, and cover-letter framing obvious before you open the portal.
Stage | What to check |
|---|---|
1. Scope | Scope check |
2. Package | Formatting check |
3. Cover letter | Editorial screening |
4. Final check | Peer review |
Quick answer: This Journal of Statistical Software submission guide is for statistical-software manuscripts where the paper, package, source code, examples, documentation, and replication materials need to work together.
Submit when the manuscript explains the statistical technique, the implementation, the code interface, and reproducible examples for a broad statistical-computing audience.
From our manuscript review practice
For JSS, the first-read question is whether the paper and software jointly advance statistical computing, not whether the repository merely works.
How was this page reviewed?
Source check, May 26, 2026: this page was reviewed against the official JSS submission page, submission guide, about page, editorial-team page, DOI announcement, and recent JSS article records. This source pass anchors the public facts used below.
Evidence boundary: public sources verify the open-source and open-access model, submission-system expectations, paper-plus-code positioning, editorial-team page, recent DOI pattern, and title, abstract, and contributor intake fields, but they do not reveal private editorial notes or manuscript-specific reviewer decisions. The page translates those sources into code-readiness, reproducibility, and paper-software fit checks.
Run a Journal of Statistical Software pre-submission readiness check before upload, or use the checks below manually.
For a fast first pass on software and reproducibility fit, run the Manusights readiness review. How this page was reviewed: Manusights editorial analysis identifies three failure patterns across statistical software, R packages, Python packages, reproducible examples, simulation studies, computational methods, and applied-statistics tools plus official JSS source checks. In practice, editors specifically screen for abstract, methods, figure, cover letter, and reference-list signals before full review.
Use this guide when the decision is whether a manuscript should enter the Journal of Statistical Software process now or be redirected to Journal of Open Source Software, The R Journal, SoftwareX, Bioconductor, CRAN documentation, or an applied statistical-methods journal first. For baseline journal context, see the Journal of Statistical Software journal profile.
Concrete source facts used in this update include the official JSS submission system at Jstatsoft author instructions, the submission guide at Jstatsoft author instructions, DOI prefix 10.18637, recent DOI examples 10.18637/jss.v115.i04, 10.18637/jss.v115.i03, and 10.18637/jss.v112.i03, the guide's warning that manuscripts longer than 30 pages typically require much longer review times, and the editorial team listed on the editorial-team page.
Verify the current editorial team on the JSS site before quoting any name in a cover letter.
We see the same pattern in manuscript-specific diagnostics: a statistical-software paper can have a usable repository and still miss JSS if the manuscript does not show why the software changes statistical computing practice.
What is the real JSS submission decision?
JSS describes itself as an open-source and open-access scientific journal by the statistical software community. Its own guide says the typical JSS paper explains the statistical technique, the code, the actual code use, and examples. That makes the submission decision different from a standard methods paper and different from a short software notice.
The central question is whether the manuscript and software form one reproducible scholarly object. If the paper reads like documentation with references, the contribution is too thin. If the paper reads like a statistical-methods article with a repository attached, the software may be under-reviewed. JSS is strongest when the statistical idea, implementation, documentation, examples, tests, and replication materials are mutually reinforcing.
What official requirements matter before upload?
Requirement | Source fact | Submission implication |
|---|---|---|
Submission system | JSS uses its own online submission flow | Prepare title, abstract, contributors, paper, code, and files before upload |
Journal model | JSS is open-source, open-access, free-submission, and volunteer-run | Do not pitch it as a conventional APC journal |
Paper shape | The guide expects statistical technique, code, actual code, and examples | Write for users and statisticians, not only developers |
Initial size constraint | No fixed word cap is the operating rule, but manuscripts longer than 30 pages typically take much longer to review | Keep the paper concise and move extended examples or derivations into reproducible supplements |
Code and data | JSS publishes software and replication code for empirical results | Reproducibility is part of the article, not an appendix |
Editorial team | The site lists editors-in-chief and technical editorial roles | Verify current names before any personalized cover-letter claim |
This guide tells you what Journal of Statistical Software editors look for; the review tells you whether your paper passes that bar before upload. Manusights reviews 1,000+ manuscripts and reports, we do not train models on your manuscript text, and the statistical-software review includes a 60-day money-back guarantee when the deliverable is not met.
What files should be ready for JSS submission?
Artifact | What it should prove | Source boundary |
|---|---|---|
Manuscript PDF and source | The statistical technique, implementation, code use, and examples form one article | Official JSS submission guide |
Software package or source code | The package installs and exposes the functions, commands, or interface described in the paper | Official JSS submission guide |
Replication files | Tables, figures, simulations, or empirical examples can be regenerated by a reviewer | Official JSS submission guide plus Manusights review patterns |
Data availability or external-data note | Data, seeds, versions, dependencies, and external files are documented clearly | JSS reproducibility model |
Supplementary material | Extended examples, large outputs, and additional derivations are separated from the main article when they would slow review | JSS reproducibility model |
Cover letter | The paper explains why JSS is better than JOSS, The R Journal, SoftwareX, or a methods journal | Manusights venue-routing review patterns |
Contributor, ORCID, conflicts, and funding details | Authors, affiliations, funding statement, conflicts of interest, and ORCID information are ready if requested by the online submission flow | Official JSS submission page |
JSS editorial triage timeline
Day 0: Online submission intake
Upload the manuscript, source files, code package, replication materials, title, abstract, contributors, and metadata through the official JSS submission system at Jstatsoft author instructions.
Days 1 to 14: Scope and completeness screen
Editors assess whether the manuscript is a JSS paper rather than documentation, a compact software note, or an applied-methods paper with a repository attached. The abstract, introduction, examples, and code package need to make the statistical-computing contribution visible.
Weeks 3 to 8: Technical and editorial routing
JSS routing often depends on the software ecosystem and method class. Reviewers need the paper, package documentation, examples, and replication scripts to use the same terminology and expected outputs.
Weeks 8 to 20: Review and reproducibility pressure test
Reviewers inspect statistical value, code usability, computational burden, dependencies, documentation, and reproducibility. Long manuscripts or packages with hard-to-run examples can extend review substantially.
Months 5 and beyond: Revision, copyediting, and publication package
Accepted JSS articles are published with software and replication materials as part of the scholarly object. Revision work should keep the paper, source code, examples, and documentation synchronized.
Source limitations: official Journal Of Statistical Software journal and publisher pages define scope, article types, and submission mechanics, but they do not publish manuscript-level desk decisions for Journal Of Statistical Software; the patterns below combine public guidance, recent issue review, and anonymized Manusights pre-submission review work for this journal family.
Decision risks before submitting to Journal of Statistical Software
Across Manusights submission reviews for R, Python, Julia, statistical-computing, simulation, visualization, Bayesian, machine-learning, psychometric, econometric, and biostatistical software manuscripts targeting Journal of Statistical Software, the recurring problem is not that the package is unusable. It is that the paper, software, documentation, and replication materials do not yet prove a JSS-level statistical-software contribution.
The software works but the statistical contribution is underspecified
For manuscripts targeting Journal of Statistical Software, this pattern appears when the repository is useful but the abstract and first section never make the statistical contribution clear. JSS readers need to know what statistical technique, computational workflow, model class, inference problem, simulation design, diagnostic, visualization, or data-analysis task the software advances. A working package is not enough when the paper cannot explain the statistical problem it solves.
The manuscript components to test are the abstract, package overview, methods section, examples, figures, vignettes, API documentation, and references. The abstract should name the statistical problem and the software contribution. The methods section should explain the model, estimator, algorithm, diagnostic, simulation scheme, or computational design before users reach code examples. Figures and examples should show why the implementation changes practice, not only that commands run. The cover letter should explain why JSS is a better target than JOSS, The R Journal, SoftwareX, or an applied field journal.
If the contribution is mainly software engineering, JOSS may be better. If it is primarily an R-community package note, The R Journal may fit. JSS remains credible when the paper and package jointly advance statistical computing.
Check whether your JSS software paper has a statistical contribution →
Reproducibility files are present but not reviewer-complete
For manuscripts targeting Journal of Statistical Software, the second pattern appears when authors include code and data but do not make the results easy to reproduce. A reviewer should be able to understand package installation, dependencies, versions, computational burden, random seeds, example data, and expected outputs without guessing from the repository.
The component-level check is practical. The methods should describe the computational environment and dependency logic. The paper should align examples with exported functions or commands. The package documentation should match the manuscript terminology. Replication files should regenerate tables, figures, simulations, or empirical examples where possible. The README or vignette should help a reviewer run the central example. If large data files are external, the manuscript or supplement should explain where they live and what is needed to recreate the analysis.
This pattern affects routing. A manuscript with useful code but light reproducibility may belong first in a package ecosystem review process such as CRAN, Bioconductor, or PyPI. A statistical method with only illustrative software may fit a methods journal. JSS should remain the target when reproducible software and statistical explanation are inseparable.
Check whether your JSS reproducibility package is reviewer-complete →
The examples demonstrate usage but not statistical value
For manuscripts targeting Journal of Statistical Software, the third pattern is an example section that behaves like a tutorial but not a scholarly demonstration. Commands, screenshots, and output tables may show the user interface, but the manuscript does not show why the package improves analysis, inference, diagnostics, simulation, visualization, or pedagogy.
The manuscript should align each component. The abstract should state the statistical value. Examples should use data or simulations that reveal the package's advantage. Figures should compare output, diagnostics, or workflow clarity against existing approaches when appropriate. The reference list should engage statistical and software literature, not only application papers. The conclusion should be honest about limitations, maintenance, and when another tool is better.
Nearby venue choice matters. JOSS is often better for a compact software paper. The R Journal may be better for R-specific package communication. Computational Statistics, Statistics and Computing, or Journal of Computational and Graphical Statistics may fit method-led work. JSS should remain the target when examples make the statistical computing contribution visible.
How should JSS be compared with nearby journals?
Venue | Better fit when | Think twice when | Main artifact |
|---|---|---|---|
Journal of Statistical Software | Paper and software jointly advance statistical computing | The repository works but the statistical contribution is thin | Article plus reproducible software package |
Journal of Open Source Software | The main contribution is reusable open-source software | The paper needs deep statistical-method explanation | Compact software paper and repository |
The R Journal | The contribution is mainly R-community package communication | The method and software have broader statistical-computing reach | R package article and examples |
SoftwareX | Software artifact and impact statement are central | Statistical-method exposition needs full scholarly treatment | Software article and impact statement |
Statistics and Computing | Algorithmic or computational statistics contribution leads | The software package is the main scholarly object | Method paper with implementation evidence |
Should you submit now?
Readiness check
Run the scan against the requirements while they're in front of you.
See score, top issues, and journal-fit signals before you submit.
Submit If
- the abstract names the statistical problem and software contribution
- package documentation, examples, and manuscript terminology are aligned
- code, data, seeds, dependencies, and versions support reproducibility
- examples demonstrate statistical value rather than only usage
- the cover letter explains why JSS is better than JOSS, The R Journal, SoftwareX, or a methods journal
Think Twice If
- the repository is useful but the abstract reads like documentation
- the example code cannot reproduce the main table, figure, method, or simulation
- the methods section hides dependency, version, or computational-burden details
- the manuscript is mostly an applied case study with a package attached
- the paper would be clearer as a compact JOSS submission or a statistical-methods article
Final checklist before submission
- Rewrite the abstract around the statistical-computing contribution.
- Make the central example runnable from a clean environment.
- Align package documentation, function names, figures, and manuscript terminology.
- Add reproducibility notes for data, seeds, versions, dependencies, and external files.
- Use the cover letter to solve JSS fit rather than to advertise the repository.
Before you upload, run a Journal of Statistical Software submission readiness check to test statistical contribution, reproducibility, examples, documentation, and adjacent-journal fit.
Related submission guides
Use these nearby guides when the target journal is still uncertain:
How this Journal Of Statistical Software guide was checked
For the related journal overview, see Journal Of Statistical Software submission guide. In our work on Journal Of Statistical Software submissions, we observe that editors specifically screen the abstract, first figures, cover letter, and evidence package for whether the manuscript answers the journal's stated fit test; our analysis of Journal Of Statistical Software pages treats those checks as submission-risk signals, not as official guidance.
Frequently asked questions
Submit through the JSS online submission system after preparing the manuscript, source code, replication materials, contributors, title, abstract, and package documentation. The submission should make the statistical method and software implementation useful to a broad statistical-computing audience.
JSS publishes articles on statistical software along with source code and replication code for empirical results. It emphasizes open-source, open-access, reproducible software that supports statistical computing in practice.
JSS describes itself as free-submission and free-subscription open access. Authors should still verify current policy on the official JSS site before submission.
Common problems include software that is useful but not a statistical-method contribution, code and examples that are not reproducible, package documentation that does not match the paper, and a better fit for JOSS, The R Journal, SoftwareX, or an applied-methods journal.
Sources
Before you upload
Choose the next useful decision step first.
Move from this article into the next decision-support step. The scan works best once the journal and submission plan are clearer.
Use the scan once the manuscript and target journal are concrete enough to evaluate.
Anthropic Privacy Partner. Zero-retention manuscript processing.