Skip to content
pachterlabPublic

About

πŸ“ Automated manuscript validation and submission portal completion

Resources

Contributing

Security policy

Stars

214 stars

Watchers

5 watching

Forks

Latest commit

Β 

History

184 Commits

Folders and files

NameName
Last commit message
Last commit date
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

PaperPush logo

PaperPush

A toolkit and AI companion for scientific publishing
Prepare manuscripts for submission to preprint servers, journals, and conferences with just a few commands.

Website Documentation Status PyPI - Downloads PyPI version Tests License

PaperPush provides the following services:

  • A standardized system to share all metadata submitted to a venue (the .sub file - see an example here)
  • Extensive venue-specific manuscript guideline checking including section lengths, reference hallucination, figure resolution, link validation, anonymization, and much, much more β€” 186 distinct validation check types in total. See the full list

Install

For AI agent skills and CLI usage:

pip install paperpush["all"]  # Recommended β€” for AI API usage, MCP server, local web deployment, and additional manuscript validation checks
pip install paperpush  # basic CLI usage

(Required for submit): To install the playwright dependency and the required chromium browser, run:

playwright install chromium

Quickstart

Choose your favorite mode: AI agent plugin skills, website, or command line. All modes support venue-specific metadata collection, venue-tailored checking, and submission portal filling for supported venues. AI agents support additional tasks.

AI agent plugin skills

Install in Claude Code (other AI agents listed below)

  • /plugin marketplace add pachterlab/paperpush
  • (In a new session): /plugin install paperpush@paperpush

Venue-specific metadata collection, venue-tailored checking, and submission portal filling for a supported venue

  • /paperpush-prepare-submission Prepare my manuscript in /PATH/TO/MANUSCRIPT/DIRECTORY for submission to VENUE with PaperPush.

Venue-specific metadata collection and venue-tailored checking for an unsupported venue

  • /paperpush-prepare-submission Prepare my manuscript in /PATH/TO/MANUSCRIPT/DIRECTORY for submission to VENUE_NAME with PaperPush.

Choosing a venue

  • /paperpush-pick-venue Suggest venues for my manuscript in /PATH/TO/MANUSCRIPT/DIRECTORY with PaperPush.

General manuscript checking

  • /paperpush-validate Validate my manuscript in /PATH/TO/MANUSCRIPT/DIRECTORY with PaperPush.

Manuscript venue transfer reformatting

  • /paperpush-transfer Transfer my manuscript in /PATH/TO/MANUSCRIPT/DIRECTORY to NEW_VENUE with PaperPush.

Respond to reviewers

  • /paperpush-respond-to-reviewers Prepare my response to reviewers in /PATH/TO/MANUSCRIPT/DIRECTORY with PaperPush.

Website

paperpush.onrender.com

No installation required.

Venue-specific metadata collection, venue-tailored checking, and submission portal filling for a supported venue

  • Visit paperpush.onrender.com
  • Select the VENUE (or upload a .sub file)
    • For general manuscript checks, select "General"
  • Upload manuscript files and fill out the metadata fields
  • Click the blue "Validate" button to validate the files and metadata against author guidelines
  • Click the blue "Share" button to share the editable form with co-authors (or download and share the .sub file)
  • (If available) Click the "Fill out submission portal automatically" button and follow the instructions

Command line interface

Venue-specific metadata collection, venue-tailored checking, and submission portal filling for a supported venue

  • paperpush subfile VENUE # create a .sub file (paperpush subfile general if you have not chosen a venue yet)
  • Fill out VENUE.sub.txt # or agent skill /paperpush-autofill
  • paperpush validate VENUE.sub.txt # validate the files and data in VENUE.sub.txt # or agent skill /paperpush-validate
    • For general manuscript checks, run: paperpush validate --manuscript MANUSCRIPT ...
  • Share VENUE.sub.txt with co-authors (it can be viewed in a text editor, with paperpush web VENUE.sub.txt, or via upload onto paperpush.onrender.com)
  • (If available) paperpush login VENUE # log in to the VENUE submission portal
  • (If available) paperpush submit VENUE.sub.txt # fill out the VENUE submission portal with information in VENUE.sub.txt # or agent skill /paperpush-submit
    • Or run every step above in one command: paperpush prepare-submission VENUE -p MANUSCRIPT_DIR (autofills through an LLM API key)
    • submit is for initial submissions only. Upload a revision through the venue's own "submit revision" link for the existing manuscript (prepare it with /paperpush-respond-to-reviewers)

PaperPush workflows

Use with AI

Install the paperpush plugin for your agent:

Claude Code (two separate prompts):

/plugin marketplace add pachterlab/paperpush
/plugin install paperpush@paperpush

Codex:

codex plugin marketplace add pachterlab/paperpush
codex plugin add paperpush@paperpush

From a pip install (any agent):

paperpush install-skills                 # Claude Code, every project (~/.claude/skills)
paperpush install-skills --agent codex   # Codex (~/.codex/skills)
paperpush install-skills --dest DIR      # any other agent's skills directory

Then ask:

/paperpush-prepare-submission Prepare my manuscript in /PATH/TO/MANUSCRIPT/DIRECTORY for submission to VENUE with PaperPush.

See docs/example-session.md for a full worked example of this flow.

CLI usage

Use the agent skill /paperpush-prepare-submission to run this entire pipeline.

  1. paperpush subfile VENUE: creates a file VENUE.sub.txt that is a template for the VENUE submission. Fields are grouped into the same sections for every venue (manuscript type, files, details, authors, reviewers, declarations, additional); add --venue-order to list them in the order the venue's portal asks for them instead.
  2. fill out VENUE.sub.txt: Open VENUE.sub.txt in a text editor to edit manually, or run paperpush web VENUE.sub.txt to edit in a web browser. Use the agent skill /paperpush-autofill My manuscript files are in /PATH/TO/MANUSCRIPT/DIRECTORY. Fill out VENUE.sub.txt or the command paperpush autofill --engine api -p /PATH/TO/MANUSCRIPT/DIRECTORY ... VENUE.sub.txt (API) to automatically fill from the manuscript directory with AI. paperpush autofill requires the provider's API key. The AI agent may not be able to fill out all fields if some information is not in the manuscript directory.
  3. paperpush validate VENUE.sub.txt: run the pre-submission checks on the filled VENUE.sub.txt. Use the agent skill /paperpush-validate or the CLI flag --ai (API) to run checks with AI. The AI checks require the provider's API key. To check files without a .sub, name them instead: paperpush validate --manuscript main.tex --title-page title.tex --figures fig1.png fig2.png ... runs the checks that apply to any manuscript (links, references, hidden text, citation order, prose, etc.), and adding --venue VENUE checks them against that venue's author guidelines too. Use the agent skill /paperpush-fix to fix the issues validate finds: it edits the manuscript sources and the .sub, validates again until nothing fixable is left, and reports what needs your decision.
  4. paperpush login VENUE: log in to the VENUE submission portal. Add --browser to type the username and password into a one-time page in your browser instead of the terminal (this is how an AI agent signs you in without seeing the password). (Optional: pass --manual-login to submit instead to sign in by hand in its browser window, with nothing stored.)
  5. paperpush submit VENUE.sub.txt: Fill out the VENUE submission portal. Will not actually submit the manuscript. We highly recommend reviewing the submission form in the venue portal before clicking submit. Use the agent skill /paperpush-submit to run login and submit on a .sub file. Use the agent skill /paperpush-portal-debug or the CLI flag --ai (API) to have AI fix any issues that may arise. Ignore validation checks with the --skip-validate flag. Use submit only for initial submissions: it opens a new submission, so a revision sent this way becomes a duplicate. Upload revisions through the venue's own "submit revision" link instead (/paperpush-respond-to-reviewers prepares the revised manuscript, marked manuscript, and response to reviewers). submit warns and asks before continuing when the .sub is in a revisionN/ directory or sits beside a response-to-reviewers document (--yes skips the question).

Helper commands:

  • paperpush venues: List supported venues.
  • paperpush publishers: List the publishers whose house rules back their venues' own guidelines. Where a venue's guidelines are silent, its publisher's house rules apply, reported as warnings.
  • paperpush update-venues: Update the venue data (venues.json, submission_forms.json, manuscript_requirements.json) from the remote venue-data branch.
  • paperpush requirements VENUE: print VENUE's author guidelines, if available. Rules marked * come from its publisher's house rules.
  • paperpush pick-venue: List journals and conferences that are a good thematic fit for your manuscript. Give keywords, the manuscript, or its --title and --abstract. By default it searches any journal or conference, through the works most similar to yours in OpenAlex, and marks the ones PaperPush supports. Conferences show their CORE/CCF rank, next deadlines, paper or abstract, length limit, and whether they are archival (from conference-agent, CORE, and ccfddl). --venue-type journal|conference picks one kind, archival conferences are listed by default, --non-archival lists only abstract and poster meetings, and --archival all lists both, and --paperpush-supported-only ranks only the venues supported in PaperPush (offline). It only checks for thematic fit, not impact or likelihood of acceptance.
  • paperpush format VENUE.sub.txt: reformat the manuscript (.docx or LaTeX) for VENUE. It first looks for the venue's own Word or LaTeX template (the recorded template link, then the venue's author-guideline pages) and applies it; without one it applies the venue's layout rules (page size, margins, font, spacing, line and page numbers). The original is never changed; the result and a CHANGES.md go to a new directory. --list-templates only shows the templates found.
  • paperpush convert --manuscript FILE --to docx|tex: convert a manuscript from Markdown to Word or LaTeX, or between Word and LaTeX. Equations become editable Word equations, citations and cross-references stay live, and a .docx made from LaTeX converts back with every unedited block restored exactly. --no-source leaves the LaTeX out of a .docx bound for a journal. The result and a CONVERSION.md, which compares source and output, go to a new directory.
  • paperpush find-reviewers VENUE.sub.txt: Suggest peer reviewers who recently published similar work (from OpenAlex), leaving out the manuscript's authors, their recent co-authors, colleagues at their institutions, and anyone you --exclude. --write adds the suggestions to the .sub's reviewer field; fill in their e-mail addresses, which OpenAlex does not have.
  • paperpush options VENUE.FIELD: print the allowed values for FIELD in VENUE's submission form.
  • paperpush web VENUE.sub.txt: open a sub file in a local deployment of the web application

See the YouTube tutorial PaperPush Tutorial

Documentation

paperpush.readthedocs.io

Supported venues

paperpush validate --manuscript main.tex runs general-purpose checks (links, references, hidden text, citation order, prose, ...) on any manuscript, whether or not its venue is listed below.

Preprint servers

Venue Slug Validate + basic .sub Submit + full .sub
alphaXiv alphaxiv βœ… βœ…
arXiv arxiv βœ… βœ…
bioRxiv biorxiv βœ… βœ…
medRxiv medrxiv βœ… βœ…

Journals

Venue Slug Validate + basic .sub Submit + full .sub
AJHG ajhg βœ…
Bioinformatics bioinformatics βœ… βœ…
BMC Bioinformatics bmc_bioinformatics βœ… βœ…
BMC Biology bmc_biology βœ…
BMC Genomics bmc_genomics βœ…
BMC Medicine bmc_medicine βœ…
The BMJ bmj βœ…
Cell cell βœ… βœ…
Cell Genomics cell_genomics βœ… βœ…
Cell Reports cell_reports βœ…
Cell Reports Methods cell_reports_methods βœ…
Cell Stem Cell cell_stem_cell βœ…
Cell Systems cell_systems βœ… βœ…
Combinatorica combinatorica βœ… βœ…
Communications Biology communications_biology βœ…
Discrete Mathematics discrete_mathematics βœ… βœ…
eLife elife βœ…
European Radiology european_radiology βœ…
Frontiers in Bioinformatics frontiers_bioinformatics βœ…
Frontiers in Genetics frontiers_genetics βœ…
Frontiers in Immunology frontiers_immunology βœ…
Genome Biology genome_biology βœ… βœ…
Genome Medicine genome_medicine βœ…
Genome Research genome_research βœ…
IEEE TMI ieee_tmi βœ…
IEEE TNNLS ieee_tnnls βœ…
IEEE TPAMI ieee_tpami βœ…
iScience iscience βœ…
JAMA jama βœ…
JIIM jiim βœ…
JMLR jmlr βœ…
JNM jnm βœ…
The Lancet lancet βœ…
Lancet Digital Health lancet_digital_health βœ…
Medical Image Analysis medical_image_analysis βœ…
Molecular Cell molecular_cell βœ…
NAR Cancer nar_cancer βœ…
NAR Genomics and Bioinformatics nar_genomics_bioinformatics βœ…
Nature nature βœ… βœ…
Nature Biomedical Engineering nature_biomedical_engineering βœ… βœ…
Nature Biotechnology nature_biotech βœ… βœ…
Nature Cell Biology nature_cell_biology βœ…
Nature Communications nature_communications βœ…
Nature Computational Science nature_computational_science βœ…
Nature Genetics nature_genetics βœ…
Nature Machine Intelligence nature_machine_intelligence βœ… βœ…
Nature Medicine nature_medicine βœ…
Nature Methods nature_methods βœ… βœ…
Nature Neuroscience nature_neuroscience βœ…
Nature Structural & Molecular Biology nature_structural_molecular_biology βœ…
NEJM nejm βœ…
Neuron neuron βœ…
npj Digital Medicine npj_digital_medicine βœ…
Nucleic Acids Research nucleic_acids_research βœ… βœ…
Patterns patterns βœ…
PLOS Biology plos_biology βœ…
PLOS Computational Biology plos_compbio βœ… βœ…
PLOS Genetics plos_genetics βœ…
PLOS Medicine plos_medicine βœ…
PLOS ONE plos_one βœ…
PNAS pnas βœ…
Radiology radiology βœ…
Radiology: Artificial Intelligence radiology_ai βœ…
Science science βœ… βœ…
Science Advances science_advances βœ… βœ…
Science Immunology science_immunology βœ… βœ…
Science Robotics science_robotics βœ… βœ…
Science Signaling science_signaling βœ… βœ…
Science Translational Medicine science_translational_medicine βœ… βœ…
Scientific Reports scientific_reports βœ…
TMLR tmlr βœ…

Conferences

Venue Slug Validate + basic .sub Submit + full .sub
ACL Rolling Review acl_arr βœ…
CVPR 2027 cvpr_2027 βœ…
NAACL 2027 Demo Track naacl_2027_demo βœ… βœ…

Data repositories

Venue Slug Validate + basic .sub Submit + full .sub
CaltechDATA caltechdata βœ… βœ…
GEO geo βœ…
SRA sra βœ… βœ…
Zenodo zenodo βœ… βœ…

View the list on the command line with paperpush venues. See more information on major conferences at conference-agent.

Venues are added (for validate) and updated (for validate and submit) daily. paperpush update-venues updates immediately.

New venues are added for submit with paperpush releases - pip install -U paperpush.

Adding new venues

Each venue is listed in paperpush/venues.json (the master list of venues and their general metadata), paperpush/manuscript_requirements.json (the manuscript guidelines), and paperpush/submission_forms.json (the fields the portal asks for). The script for automatic venue login and submission lives in /paperpush/venues/PLATFORM/VENUE.py in a VENUE class with methods login and submit. See CONTRIBUTING.md and DEVELOPMENT.md for more details.

AI Skills

Skill Use it to Example prompt
/paperpush-pick-venue suggest venues for a manuscript: journals that publish similar work, checked against your constraints (open access, APC budget) and each supported venue's limits, then hand the chosen one to /paperpush-prepare-submission /paperpush-pick-venue Where should I submit my manuscript in /PATH/TO/MANUSCRIPT/DIRECTORY? It must be open access with an APC under $3000.
/paperpush-prepare-submission go from a manuscript directory to a filled-in portal (autofill, validate, login and submit if supported) /paperpush-prepare-submission Prepare my manuscript in /PATH/TO/MANUSCRIPT/DIRECTORY for submission to VENUE.
/paperpush-autofill fill a .sub from the manuscript files /paperpush-autofill My manuscript files are in /PATH/TO/MANUSCRIPT/DIRECTORY. Fill out VENUE.sub.txt.
/paperpush-validate run every check, including the ones that need a reader /paperpush-validate Validate VENUE.sub.txt and save the report as REPORT.pdf.
/paperpush-fix fix what validate flags (in the .tex/.docx sources and the .sub), re-validate until nothing fixable is left, and report what needs the author /paperpush-fix Fix the issues validate found in VENUE.sub.txt.
/paperpush-login log in to the portal /paperpush-login Log in to VENUE.
/paperpush-login sign in to a venue without typing the password into the chat: opens a one-time sign-in page on your computer, checks the login against the venue, and stores it; also checks or removes a stored login /paperpush-login Log me in to VENUE.
/paperpush-submit log in and fill in the portal from a ready .sub (optionally skipping validation) β€” invokes /paperpush-portal-debug if it stalls /paperpush-submit Fill out the VENUE submission portal from VENUE.sub.txt.
/paperpush-portal-debug get a stalled paperpush submit run unstuck /paperpush-portal-debug paperpush submit VENUE.sub.txt is stuck at the STEP step.
/paperpush-transfer reformat a manuscript from one venue to another: copy the files into a new <venue>/ directory, create and autofill its .sub (reusing earlier .sub files), validate, and write transfer.txt describing the changes /paperpush-transfer My manuscript in /PATH/TO/MANUSCRIPT/DIRECTORY was rejected from OLD_VENUE. Transfer it to NEW_VENUE.
/paperpush-respond-to-reviewers prepare a revision in two phases: (1) copy the manuscript and reviews into a new revisionN/ directory (e.g., revision1, revision2, etc.) and propose a plan for each comment, then (once you approve) (2) revise the manuscript; write the response to reviewers, the clean revised manuscript, and a marked manuscript; and validate the revised manuscript /paperpush-respond-to-reviewers The reviews for my manuscript in /PATH/TO/MANUSCRIPT/DIRECTORY are in REVIEWS_FILE. Prepare the revision.
/paperpush-add-venue-validate add or refresh a venue's author guidelines (contributors) /paperpush-add-venue-validate Add VENUE's author guidelines from GUIDELINES_URL.
/paperpush-add-venue run /paperpush-add-venue-validate and add login and submit support for a venue, with tests (contributors) /paperpush-add-venue Add login and submit support for VENUE.

PaperPush schematic

What is a .sub file

The .sub file is the yaml-like text file that contains all metadata and file paths required to upload a manuscript onto a venue's submission portal. An example snippet is shown below. In this case, you would provide "/PATH/TO/MANUSCRIPT.pdf", "TITLE", and "HERE IS THE ABSTRACT".

@venue: venue

# Manuscript file (file, REQUIRED)
#   Path to the submission.
manuscript_file: /PATH/TO/MANUSCRIPT.pdf

# Title (text, REQUIRED)
#   The full title of the article.
title: TITLE

# Abstract (textarea, REQUIRED)
#   Plain-text abstract, at least 20 characters
abstract: |
  HERE IS THE ABSTRACT

See a full, filled-in example here (from tests/sub_files/arxiv/arxiv.sub.txt).

MCP server

To drive paperpush from any MCP client β€” Claude Desktop, an IDE extension β€” run it as an MCP server:

pip install 'paperpush[mcp]'
{
  "mcpServers": {
    "paperpush": {
      "command": "paperpush-mcp"
    }
  }
}

The server exposes the whole pipeline as tools. See AGENTS.md for the tool list and the contract agents should follow.

Comparison with other tools

PaperPush compared with other manuscript tools

Green means supported, amber means partial, red means not supported, and grey means unknown. The data reflect what each tool advertises (see the sources in the script), so let us know if something has changed. PDF version. Regenerate with python scripts/gen_comparison_table.py.

FAQ

How does PaperPush work?

Supported venues are listed in paperpush/venues.json, their submission form data are in paperpush/submission_forms.json, and their author guidelines are in paperpush/manuscript_requirements.json. paperpush subfile generates a file from the form for the specified venue. The file can be filled out manually, or with the help of an LLM via paperpush autofill. The manuscript documents are validated with paperpush validate. The submission portal for a selected venue is filled out with the information from this file with a paperpush submit. This runs a Playwright script that is written specifically for each supported venue.

The repository says that it supports a given venue, but it fails when I try. Why is that?

Here are a few possibilities, in order of decreasing ease of resolution:

  • Sometimes, submission portals can be a bit funny, and the solution can be as simple as retrying the command 1-2 more times.
  • The submission portal is having server issues. You can try logging in to the portal manually to see if it is working, as well as on a different browser and at a different time.
  • The sub file has an option that we did not anticipate. You can try running the unit test for the venue with pytest tests/test_submit.py --run-portal -s --venue VENUE. If this passes, then it indicates an option in the sub file is not being handled correctly. If this fails, then it indicates that the submission portal has changed since the last time the venue was tested. In either case, please open an issue with the error message.
  • The submission portal has changed since the last time the venue was tested. You can run the unit test listed above to see if this is the case. If so, please open an issue with the error message.

Can I still use PaperPush if my venue is not listed? Yes! PaperPush can still validate manuscript files with up to 132 general validation checks. You can do this in the following ways:

  • AI agent: Run the skill /paperpush-validate Validate my manuscript in /PATH/TO/MANUSCRIPT/DIRECTORY with PaperPush. for general checks, or /paperpush-prepare-submission Prepare my manuscript in /PATH/TO/MANUSCRIPT/DIRECTORY for submission to VENUE_NAME with PaperPush. for venue-specific checks in which the agent can retrieve guidelines from the venue's website.
  • Website: Choose the "General" venue option and upload your manuscript files/directory for general checks.
  • CLI: Run paperpush validate --manuscript MANUSCRIPT --issn ISSN (or --publisher NAME) to check against the journal's publisher's house rules, when paperpush has them (paperpush publishers); what they catch is reported as warnings. Run paperpush validate --manuscript MANUSCRIPT ... for general checks, or paperpush subfile general for a .sub with the files and metadata every venue asks for (title, abstract, keywords, authors, manuscript, figures, supplements, cover letter, ...), then fill it in and paperpush validate general.sub.txt.

I do not see my venue in the supported list. Is it possible to add a venue?

Yes! See CONTRIBUTING.md if you would like to add a journal yourself, and feel free to ask any questions in the Discussion forum.

Does PaperPush press submit for me?

No. PaperPush will bring you to one of the final steps on your venue of interest, but it will never actually press submit. I always recommend viewing any compiled PDFs and entered information to ensure accuracy and acknowledgment of guidelines.

Does every venue have a unique submission portal?

No β€” in fact, many share the same type of platform. PaperPush has a unique Playwright script for each supported venue, but many venues share the same submission platform. The big ones are Editorial Manager (including the Cell family and PLOS family), ScholarOne Manuscripts, eJournalPress, Snapp, and OpenReview (for many computer science conferences). The submission script may be highly similar for venues that share the same platform, so check the folders within paperpush/venues to see which venues share the same submission platform. See screenshots of each of the major supported venues in docs/portal_screenshots to see what each submission portal looks like.

How long does it take to add a new journal?

It depends on the complexity of the submission portal and your comfort with coding, but I would say roughly 1-3 hours manually. AI tools with the paperpush skills can potentially do this in under 20 minutes.

Can I vibe code a new journal?

Yes, with /paperpush-add-venue to add or update a venue for guideline validation and submission portal filling, or /paperpush-add-venue-validate to add or update a venue for guideline validation only (see CONTRIBUTING.md). AI agents can navigate submission portals and write the Venue class for login and submit, but it can take a lot of tokens and may stall at times, so some human oversight helps. In my experience, LLMs can make the code a bit verbose and abstract away some of the action names, which may be harder to read/maintain in my opinion, but this is just stylistic. My favorite code style is in arxiv.py.

For AI agents

If you are an AI agent asked to submit a manuscript on the user's behalf, read AGENTS.md β€” or, if you are working from a pip install rather than a clone of this repo, run paperpush --agent-guide, which prints the same document from the copy that shipped with the installed version. It describes how to run the full pipeline while doing your own field extraction (reading the manuscript and writing a values.json for the default --engine manual) rather than relying on the API-backed engine. It also asks the agent to check paperpush login --list before it starts and, when you are not signed in, to start paperpush login <venue> --browser for you: a sign-in page opens in your browser, and you type the password there, never into the chat. Agents that support skills should install them (see Use with AI); AGENTS.md lists what each skill does and when to use it.

Security and privacy

Report vulnerabilities privately as described in SECURITY.md. The website's privacy page covers what happens to uploaded files: they are deleted 24 hours after last use, and shared forms are end-to-end encrypted. The security program (policy, controls, vendors, incident response) is in security/.

License

This project is licensed under the BSD-2 License - see the LICENSE file for details.

Developed by Joe Rich

About

πŸ“ Automated manuscript validation and submission portal completion

Resources

Contributing

Security policy

Stars

214 stars

Watchers

5 watching

Forks

Releases

Packages

Contributors

Languages