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 2.2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Dependencies installed with uv, full test suite passes (407/407), ruff/ruff format pass, the CLI binary runs and prints help/version, and the Evernote API ping succeeds.

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.02 (measured)
recorded runs
2
last tested
stars
1,795
forks
136
open issues
4
watchers
22
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.

Install time
2 minutes
Cold machine to finish
under a minute
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
uv run pytest: 407 passed, 36 skipped, 10 deselected; uv run evernote-backup --help printed usage; uv run evernote-backup --version printed 1.14.0; uv run evernote-backup manage ping printed 'Connection OK!'
Model tokens used
28,848
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

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

Let me also try the `ping` command to confirm the app makes network connections as designed (and fa…
exec
/bin/sh -lc 'cd /work/repo && PATH="$HOME/.local/bin:$PATH" uv run evernote-backup manage ping 2>&1…
 succeeded in 257ms:
2026-11-13 13:16:55,349 | INFO | Connection OK!
The app connects to Evernote API successfully (we're behind a network that has access, apparently).…
exec
/bin/sh -lc 'cd /work/repo && PATH="$HOME/.local/bin:$PATH" uv run ruff format --check 2>&1' in /wo…
 succeeded in 0ms:
62 files already formatted
tokens used
28,848

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 2.2 minutes, faster than the median of the 47 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

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.

Of the 48 backup projects Argusic has installed and timed, evernote-backup was the 16th fastest to reach a running state, and 32 of 48 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 Runner2/3Runs with mocks92.000.02
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 2 minutes, hitting 0 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. 2 attempts are 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.02: 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?
2.2 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?
Nothing did, in the recorded run: zero errors between clone and running.
How does evernote-backup compare with the alternatives?
Of the 48 backup projects Argusic has installed and timed, evernote-backup was the 16th fastest to reach a running state, and 32 of 48 reached one at all.
Where is the evidence for evernote-backup?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion