openjournals

openjournals/joss

Ruby MIT Science

The Journal of Open Source Software

1.9k stars
209 forks
active
GitHub +7 / week

1.9k

Stars

209

Forks

170

Open issues

30

Contributors

AI Analysis

JOSS is a peer-reviewed academic journal and submission platform designed specifically for research software packages, filling a gap where researchers need academic credit (via DOI and citations) for software contributions. It serves researchers and software developers who want their tools recognized in academic contexts without lengthy paper-writing processes. It is not a general-purpose journal or suitable for non-software academic work.

Science Application Discovery value: 4/10
Documentation 8/10
Activity 9/10
Community 8/10
Code quality 6/10

Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.

Overall score 8/10

AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.

academic-publishing peer-review research-software doi-minting scholarly-communication
Actively maintained Well documented MIT licensed Niche/specialized use case Beginner friendly Production ready
Deep Analysis · Based on README and public signals
2d ago

JOSS: a peer-reviewed publishing platform for research software, built on Rails for academic credentialing

JOSS is an open-access academic journal specifically designed to publish research software. It operates as a formal peer-review system that issues CrossRef DOIs and provides academic credit for software contributions—solving the problem that researchers lack traditional publication venues for software work. Adoption appears concentrated among research software developers, particularly in scientific computing and data science communities. The service has published thousands of software papers since 2016, though it functions primarily as a publishing service rather than a widely-deployed tool.

Origin

JOSS was created in 2016 by Arfon Smith and others at the Open Journals project to address a gap in academic incentive structures: software contributions rarely counted toward career advancement despite being critical research infrastructure. It formalized a peer-review process specifically for software, not software papers, targeting researchers who had already built high-quality tools.

Growth

Growth appears to have stabilized following initial expansion. The project gained consistent adoption through word-of-mouth in scientific computing communities and institutional recognition of JOSS publications as valid academic output. More recently, growth has plateaued (5 stars in last 7 days as of 2026-07-08, compared to 1,890 total over ~10 years), suggesting the addressable market for a software-focused journal is largely reached. The project is sustained by NumFOCUS backing and an editorial board rather than venture growth dynamics.

In production

JOSS operates the live submission platform at joss.theoj.org and has published thousands of papers since 2016. The service is funded and maintained by NumFOCUS. However, concrete metrics on annual submissions, acceptance rates, or institutional adoption are not disclosed in README. Adoption appears real but adoption scale/growth trajectory not verified in available documentation.

Code analysis
Architecture

Appears to be a Ruby on Rails web application with PostgreSQL backend and Elasticsearch for search indexing. Based on README, the system handles submission workflows, peer review coordination, and publication metadata. The architecture likely includes integration points for CrossRef DOI minting and GitHub-based review processes (mentioned in separate joss-reviews repository). Specific design patterns are not documented in README.

Tests

Not documented in README. Build status badge shown active, suggesting CI/CD pipeline exists, but test coverage metrics not disclosed.

Maintenance

Project shows active maintenance: last push 2026-07-07 (same day as analysis date), CI/CD workflows active, and README includes recent macOS-specific fixes (dated 2024-08-15). This indicates sustained engagement rather than stagnation. However, commit frequency and issue resolution speed cannot be assessed from metadata alone. The slow star growth likely reflects steady-state operation of an established service rather than neglect.

Honest verdict

ADOPT IF: you are a research software maintainer seeking formal academic credentialing, or an institution wanting to recognize software contributions in tenure/promotion decisions, or a journal/platform wanting to learn from JOSS's peer-review workflow for software. AVOID IF: you need a general-purpose journal management system (use OJS instead), or you are building infrastructure to *host* journals rather than *publish* software, or your goal is to build a GitHub alternative. MONITOR IF: you are investigating how academic institutions are beginning to value software-as-research-output; JOSS is a working proof-of-concept that this model can sustain, but its scalability and influence on broader academic credentialing remains uncertain.

Independent dimensions

Mainstream potential

3/10

Technical importance

5/10

Adoption evidence

6/10

Risks
  • Market saturation: the addressable audience of research software developers seeking academic publication is finite and may be largely reached; growth rate suggests this
  • Dependence on academic incentive structures: if institutions stop valuing JOSS publications or migrate to other credentialing models, demand could decline
  • Sustainability: relies on NumFOCUS funding and volunteer editorial labor; loss of either could strain operations
  • Limited scope: only serves software that meets journal quality standards; does not address tool adoption/discoverability for practitioners outside academic research
  • Metadata accuracy: peer review happens in separate repository (joss-reviews); synchronization and long-term metadata integrity not documented
Prediction

JOSS will likely remain a stable, specialized credentialing system for research software within academic communities. Mainstream growth seems unlikely because it addresses a permanent niche (academic incentives for software) rather than a gap that will be filled by competing models. It may influence how other institutions design software publication workflows, but is unlikely to expand significantly beyond current user base.

0 found this helpful

Newsletter

Get analyses like this every Monday

Free weekly digest of the most interesting open-source discoveries.

Languages

Ruby
68.4%
HTML
24.4%
SCSS
4.3%
JavaScript
2.9%
Procfile
0%

Information

Language
Ruby
License
MIT
Last updated
1d ago
Created
127mo ago
Analyzed with
anthropic/claude-haiku-4-5

Stars over time

Loading…

Contributors over time

Top 100 contributors only — repos with more will plateau at 100.

Loading…

Recent releases

No releases published yet.

Similar repos

pkp

pkp/ojs

Open Journal Systems (OJS) is open-source software designed to manage scholarly...

opensource-socialnetwork

opensource-socialnetwork/opensource-socialnetwork

Open Source Social Network (OSSN) is a PHP-based social networking platform...

1.2k PHP Web Dev
IQSS

IQSS/dataverse

Dataverse is an open-source platform for research institutions to host, manage,...

1.1k Java Science
pingcap

pingcap/ossinsight

OSSInsight is an analytics engine that analyzes 10+ billion GitHub events to...

2.5k TypeScript Data
synthetic-sciences

synthetic-sciences/openscience

OpenScience is an AI-powered workbench for scientific research that automates...

2k TypeScript Science
vs. alternatives
PKP OJS (Open Journal Systems)

General-purpose open-source journal management platform; JOSS is a specialized instance optimized for software publishing, not a competing platform. OJS has broader adoption (1008 stars) for traditional academic journals.

Dataverse (IQSS)

Research data repository system; serves researchers but does not provide peer-review publication workflow or academic credentialing in the same way JOSS does. Complementary rather than competitive.

GitHub as informal credentialing

Developers sometimes cite GitHub profiles instead of publishing papers; JOSS competes against this by providing formal academic credit (DOI, indexing) that still matters for researcher careers despite GitHub's visibility.

Software Heritage / Software Preservation

Focused on archiving and preserving code; does not provide peer review or academic publication workflow. Orthogonal problem domain.

ArXiv preprints for software

Researchers sometimes post software papers to ArXiv without peer review; JOSS differentiates by offering formal peer review, CrossRef DOIs, and curation specifically designed for software quality evaluation.