evernote-backup

Backup & export all Evernote notes and notebooks

Runs with mockssource: GitHubPythonMITcommit 749c72666fac

Python, MIT licensed. The project labels itself: backup, database, enex, enex files, evernote, evernote backup, evernote client and evernote data.

evernote-backup runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.1 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

evernote-backup 1.14.0 is installed and fully functional: the CLI shows help and version, all lint/format checks pass, and 407/407 functional tests pass using mocked Evernote backends.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.01 (measured)
recorded runs
1
last tested
stars
1,757
forks
134
open issues
4
watchers
20
size
1 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • uv not found in PATH
  • ty check reports 4 unresolved-import errors for keyring and pycryptodome on Linux
Install time
under a minute
Cold machine to finish
2 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
uv run pytest exited 0 (407 passed, 36 skipped); uv run evernote-backup --version returned 'evernote-backup, version 1.14.0'
Model tokens used
17,004
Exact commit tested
749c72666fac
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- **Launch**: `uv run evernote-backup --version` returns `evernote-backup, version 1.14.0`.
- **Tests**: 407 passed, 36 skipped (platform-conditional desktop_session tests), 10 deselected (be…
- **Lint**: `ruff check` — all checks passed. `ruff format --check` — 62 files already formatted.
- **Type check**: `ty check` reports 4 expected errors on Linux for platform-conditional imports (`…
tokens used
17,004
All checks completed. Here's the full report:
- **Install**: `uv sync --all-groups` succeeded (required installing uv first via curl script).
- **Launch**: `uv run evernote-backup --version` returns `evernote-backup, version 1.14.0`.
- **Tests**: 407 passed, 36 skipped (platform-conditional desktop_session tests), 10 deselected (be…
- **Lint**: `ruff check` — all checks passed. `ruff format --check` — 62 files already formatted.
- **Type check**: `ty check` reports 4 expected errors on Linux for platform-conditional imports (`…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 0.1 minutes, faster than the median of the 17 comparable projects Argusic has measured.
  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 18 backup projects Argusic has installed and timed, evernote-backup was the 2nd fastest to reach a running state, and 13 of 18 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.01

Topics (from GitHub)

backupdatabaseenexenex-filesevernoteevernote-backupevernote-clientevernote-dataevernote-exportevernote-notesexportnotebookspythonsyncyinxiang

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/evernote-backup.svg)](https://argusic.com/subject/evernote-backup)

Questions

Does evernote-backup run?
evernote-backup runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 0 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test evernote-backup?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 749c72666fac. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test evernote-backup?
The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does evernote-backup take to install?
0.1 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does evernote-backup need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing evernote-backup?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does evernote-backup compare with the alternatives?
Of the 18 backup projects Argusic has installed and timed, evernote-backup was the 2nd fastest to reach a running state, and 13 of 18 reached one at all.
Where is the evidence for evernote-backup?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion