paper-status-monitor
Monitor the peer-review status of your Elsevier submissions and keep one Excel history per manuscript.
Elsevier journals send authors a Track your submission link
(https://track.authorhub.elsevier.com/?uuid=...) that shows the review status of a
manuscript: reviewers invited, reviews completed, last review activity, revision
number... paper-status-monitor checks those pages for you — for example every time
you log in — records every change in an Excel workbook and opens a short report when
something changes.
Paper status monitor - report
Run started: 2026-10-21 08:55:12
------------------------------------------------------------------------
CHANGES (1)
------------------------------------------------------------------------
[1st revision] A study of something important
- Status: 'Under Review' → 'Required Reviews Complete'
- Reviews completed: '1' → '2'
Journal: Journal of Examples
Manuscript number: ABC-D-26-00001R1
Tracker: https://track.authorhub.elsevier.com/?uuid=...
Workbook: C:\Users\me\Documents\paper-status-monitor\ABC-D-26-00001 - Journal of Examples - A study of something important.xlsx
Features
- No browser needed – reads the same JSON data as the official tracking page (no Selenium, ChromeDriver or Chrome).
- Excel history of every submission – every revision (R1, R2, …) is appended to
the same workbook, with a
Detected attimestamp for every change, and an optional Time in status sheet adds up how long each submission spent in each status. - Your workbook names – build them from placeholders such as
{paper},{journal}or{manuscript_number}, add your own fields (e.g.paper = "Tau") to sort them by paper, or keep all the submissions of a paper to different journals in one workbook withworkbook_name = "{paper}". - You choose what matters – decide, column by column, which changes are recorded in the workbook and which are reported: for example, record a new Last review activity date without being notified, or be notified only when the Status changes.
- Change reports, desktop notifications and e-mails – a plain-text report is written only when something you care about changes, a new submission is tracked or a check fails; it can be opened for you, announced with a desktop notification (Windows, macOS, Linux), sent by e-mail through your SMTP server, or any of these.
- Command line or window –
paper-status-monitor guiopens a graphical interface to manage submissions, notifications, workbook names and runs. - English or Spanish –
language = "es"writes the reports, notifications, e-mails and summary, and shows the window, in Spanish; the workbooks keep the same columns in every language. - Runs at login –
paper-status-monitor autostart enableadds a windowless launcher that runs at every login (a Startup shortcut on Windows, an XDG autostart entry on Linux, a launchd agent on macOS); it waits for the network and for cloud drives such as Google Drive or OneDrive to be ready, and with--every 12hit keeps checking while you stay logged in (on Windows,--trayadds an icon with the latest statuses to the notification area). - Robust – retries on network errors, atomic workbook writes, a lock against
concurrent runs, a rotating log file and a
doctorcommand to diagnose problems. - Detects the end of tracking – when the tracker stops returning data for a submission (usually after a final decision) the change is recorded once.
Quick start
pip install paper-status-monitor
paper-status-monitor init --data-dir "C:\Users\me\Documents\Paper status"
paper-status-monitor add "https://track.authorhub.elsevier.com/?uuid=<your-uuid>" --label "My paper" --field paper=Tau
paper-status-monitor run
paper-status-monitor autostart enable # check at every login
paper-status-monitor gui # optional: do all of this from a window
Try it first with the public demo submission served by the tracker:
paper-status-monitor check 00000000-0000-0000-0000-000000000000
A few lines of the configuration file go a long way:
workbook_name = "{paper} - {journal} - {manuscript_number}" # sorted by paper
notify_ignore = ["Last review activity"] # recorded, not reported
notify = ["report", "toast"] # open it and notify
Commands
| Command | Purpose |
|---|---|
init |
Create a commented configuration file. |
add LINK |
Add a submission (tracking link or UUID), with optional custom fields. |
edit |
Change the label or the custom fields of a submission (the comments of the configuration are kept). |
remove, disable, enable |
Remove, pause or resume a submission (the comments of the configuration are kept). |
list |
Show the configured submissions and their last recorded status. |
summary |
One table with the latest status of every submission (text, Markdown or HTML). |
export |
The whole recorded history as CSV or JSON, for other tools than Excel. |
check LINK |
Show the current status of one submission without saving anything. |
run |
Check every submission (once, or periodically with --every 12h, optionally with an icon in the notification area: --tray), update the workbooks and report the news. |
organize |
Rename, merge or split existing workbooks to follow the naming template. |
gui |
Open the graphical interface (also paper-status-monitor-gui). |
autostart enable/disable/status |
Run automatically at login (Windows, Linux, macOS), and optionally every few hours. |
email test/set-password |
Send a test e-mail; keep the SMTP password in the system keyring (never in the configuration). |
doctor |
Diagnose configuration, connectivity and autostart problems. |
See the documentation for the configuration reference, the workbook format, running at login and troubleshooting.
Privacy and responsible use
- Your tracking links are personal: anyone with the link can see the status of your manuscript. They are stored only in your local configuration file, and the workbooks and reports stay on your computer.
- The tool only reads the status of submissions you configure, at a low frequency (typically once per login). Please keep it that way.
- This project is not affiliated with, endorsed by or supported by Elsevier. It relies on an undocumented endpoint that may change at any time.
Contributing
Bug reports and pull requests are welcome. Read CONTRIBUTING.md and, if you use an AI coding agent, AGENTS.md. The roadmap lives in TODO.md.
License
MIT © Daniel Sánchez-García
Metadata
Release files for paper-status-monitor 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| paper_status_monitor-0.2.0.tar.gz | 229.7 kB | With provenance | Details for paper_status_monitor-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| paper_status_monitor-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for paper_status_monitor-0.2.0-py3-none-any.whl |
Total release size: 379.0 kB
Release files / paper_status_monitor-0.2.0.tar.gz
| Download URL | paper_status_monitor-0.2.0.tar.gz |
|---|---|
| Size | 229.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
24ac2fbfdc7b09dc1435b7bb5ca2065c24a18b52a7f30cf30dacf3fc4fc10740
|
|
BLAKE2b-256 checksum How to use checksums |
8a774e8f7f028c499582d5a4666c47a9a028f58f93a674b0578e63a94c203657
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logRelease files / paper_status_monitor-0.2.0-py3-none-any.whl
| Download URL | paper_status_monitor-0.2.0-py3-none-any.whl |
|---|---|
| Size | 149.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
38981aac3a63efea5ddd0683c392e658ec6245d04406c88e18ef21328cce0fa9
|
|
BLAKE2b-256 checksum How to use checksums |
bfbb22f3bb9f8958fc73923fa5fe2ef60c532d61bdadac5afed1b21e4cb200bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logSecurity for paper-status-monitor 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for paper_status_monitor-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.