mrkeyoor.comAsk

DefiLeoo/YOINKtested 02 Oct 2026commit a262dda

YOINK review

Try YOINK in a separate vault if you want dated numerical predictions and their outcomes beside your Markdown notes.

  • Install 34 s
  • Build 8 s
200/201passed, run exited non-zero
  • 38 packages
Dev Toolsevaluationupdated 31 Oct 2026
-6stars / 7d

Try YOINK if you want to check numerical predictions alongside personal Markdown notes and can inspect a failed demo assertion before adopting it. YOINK settles dated claims in Markdown notes. Our run on 2026-10-02 at commit a262dda installed and built successfully, but the test command failed. It is a candidate for a separate trial vault, not independent proof of when you made a prediction.

Verdict

Try YOINK in a separate vault if you want dated numerical predictions and their outcomes beside your Markdown notes. Our run on 2026-10-02 at commit a262dda installed and built successfully, but its test command failed on a demo headline assertion. Inspect that failure and check your own metadata and reading sources before adoption. Choose another record system if independent proof of prediction timing is required.

We ran it

Lab card: what happened when we ran YOINK
Lab card from our sandbox run
Screenshot of YOINK (github.com/DefiLeoo/YOINK)
github.com/DefiLeoo/YOINK
Install✓ · 34s38 packages · 41 MB
Build✓ · 8s
Tests✗ · 12s200 passed · 1 failed of 201 (pytest)
Known vulns0(pip-audit)
Repo48 files~5,558 lines of source · 8.9 MB · 1 CI workflows · tests dir

Answers from our run

Does YOINK build from source?

Dependencies installed in 34 seconds (38 packages), and the build succeeded in 8 seconds. We cloned commit a262dda into a clean Debian container with 3 CPUs and no project-specific setup.

Do YOINK's tests pass?

No. The project's own test command finished in 12 seconds and reported 200 passed, 1 failed (pytest).

Does YOINK have known vulnerabilities in its dependencies?

pip-audit found none in the dependency tree at the time of our run.

Who should not use YOINK?

Workflows requiring a passing test command at the reviewed commit.

What are the alternatives to YOINK?

zk, SilverBullet. Try YOINK in a separate vault if you want dated numerical predictions and their outcomes beside your Markdown notes.

Setup4/5Our sandbox completed installation in 34 seconds and the build in 8 seconds, both with exit code 0. Interactive setup was not independently established.
Docs5/5Within the supplied material, the README explains claim inputs, settlement, storage, refusals and limitations in detail. This assesses documentation specificity rather than tested feature coverage.
Community2/5Last push on 2026-09-13 and 387 stars.Editor’s note: The supplied primary extracts do not establish contributor activity, support responsiveness or the quality of community assistance.
Maturity2/5The manifest identifies version 0.1.0 as beta, and our recorded test command returned exit code 1 on a demo headline assertion.

How we score

Who it’s for

Terminal users who want capture, linked notes and prediction settlement around an Obsidian-compatible Markdown folder.
People who can specify a numerical comparison, settlement date, reading source and confidence before an outcome is known.
Python users willing to inspect the recorded failure and test representative notes before adoption.

Who it’s NOT for

Workflows requiring a passing test command at the reviewed commit.
Records that must independently prove a prediction's timing: the ledger owner can rewrite its history.
Vaults requiring a complete YAML implementation.
People seeking a model that generates predictions.
Readers expecting the README's drawn animations to be recordings of the application.

Setup reality

Our run on 2026-10-02 reviewed commit a262dda in our Python 3.12 sandbox with 3 CPUs and 8 GB of memory. Installation completed in 34 seconds and the build step in 8 seconds, both with exit code 0. The test command returned exit code 1 after 12 seconds.

The stored parser summary recorded 200 passed tests and 1 failed test. Its recorded total is 201, with 0 skipped tests and 0 errors. These are stored parser summaries, not verified exhaustive counts of unique tests. No new execution or complete-log reconciliation was performed for this correction.

The retained output names tests/test_demo.py::TheDemoVault::test_the_headline_reads_the_way_the_screenshot_shows. The actual headline included 1 due now; the expected string ended at +35 pts overconfident. That establishes a headline assertion mismatch. It does not establish comprehensive vault or settlement coverage.

Installation left 38 packages occupying 41 MB in the sandbox. That environment footprint is separate from the manifest's empty runtime dependency list. The recorded pip-audit advisory total was 0; scan coverage is unknown because no scannedPackages value was supplied. The advisory result is not a security assessment.

YOINK requires Python 3.10 or newer. The documented vault selection order is --vault, then $YOINK_VAULT, then ~/yoink-vault. Start with a separate demo vault and inspect its files before using an existing collection.

Our sandbox built YOINK, but its test command failed

Our run on 2026-10-02 reviewed commit a262dda. Installation took 34 seconds and the build step took 8 seconds; both returned exit code 0. The test command returned exit code 1 after 12 seconds. The stored parser summary recorded 200 passed tests and 1 failed test. These summaries do not establish exhaustive unique test coverage.

The retained failure is a demo headline assertion in tests/test_demo.py. The actual text included 1 due now, while the expected text stopped at +35 pts overconfident. The visible mismatch concerns headline text. It neither demonstrates damaged notes nor proves that every vault operation works.

Our harness records command success or failure, exit codes, elapsed time and parsed test counts, alongside retained output tails. The supplied record identifies our sandbox and the reviewed commit. The MrKeyoor testing methodology explains this provenance and its limits; the current methodology page does not establish which procedure revision governed this older run. This correction uses the existing record without a new execution.

The record does not establish a separate interactive terminal trial, an Obsidian interoperability exercise, live JSON-RPC settlement or a production deployment. A successful build command does not establish those outcomes. The commit's README says the demo settles from local files and the test suite never opens a socket.

Dated numerical claims are the reason to try it

YOINK settles dated claims in Markdown notes. Its documented claim fields specify the prediction, settlement date, reading source, numerical comparison and confidence. Settlement writes the outcome, reading, timestamp and source information into the note itself. That keeps a prediction and its recorded result together without moving the notes into a proprietary format.

The YOINK README documents JSON files, dated CSV values, public-chain JSON-RPC readings and manually entered values associated with a URL. An unreadable source leaves a claim open. A manual reading preserves the address and number supplied by the user; it does not independently verify that number.

Settled claims contribute to a Brier score and a comparison between stated confidence and accuracy. The README's forecasting figures belong to a fixed demo, not a person's forecasting record. They do not show that using YOINK improves forecasting. The program records and grades predictions; the README says it has no predictive model.

Obsidian can remain the editor; the ledger remains personal

The README describes Markdown files with frontmatter and wikilinks that Obsidian can open. YOINK can therefore be considered a complement to an Obsidian workflow: its terminal adds capture, settlement and scoring around the same folder. Our sandbox record does not independently verify that interoperability. Try representative notes first, especially if they contain complex metadata, because YOINK implements a frontmatter subset rather than full YAML.

The README says whoever holds the ledger file can rewrite it end to end. Hash chaining can expose an individual edit, but it cannot independently prove when a prediction was made. That is a consequential limit if someone else must rely on the record. For personal review, the ledger can still provide a history whose individual edits are detectable.

The README also distinguishes a captured terminal still from three drawn animations. The animations explain the demo data rather than record application behavior. In particular, the animated graph does not establish a separate terminal pane reachable by a key.

Choose alternatives by the workspace you need

Choose zk for a command-line assistant to a plain-text Zettelkasten or personal wiki. Its README describes templates, search, links and editor integration, and explicitly says zk is not a note editor. It is an alternative for managing linked notes; the supplied evidence does not establish an equivalent prediction-settlement workflow.

Choose SilverBullet for a browser-based Markdown editor programmable with Lua. Its README describes wiki links, a built-in database and queries. That makes it an alternative workspace when browser editing and programmability matter more to your decision. The supplied evidence does not establish equivalent forecasting features or automatic migration from a YOINK vault.

Editorial scores and their limits

Setup ease is 4/5: our sandbox completed installation and the build, while interactive setup remains unverified. Documentation is 5/5 within the supplied material: the README explains claim inputs, storage, refusals and explicit limits. This rates documentation detail, not tested feature coverage. Maturity is 2/5: the package manifest identifies version 0.1.0 as beta, and our recorded test command failed. Community is unassessed because the supplied primary extracts do not establish contributor activity or support responsiveness.

The rubric is 1 for a major demonstrated obstacle, 2 for substantial limitations, 3 for usable with material caveats, 4 for strong evidence with a remaining caveat, and 5 for thorough evidence within the stated assessment scope. A null score means the evidence does not support an assessment. These are editorial judgments, not benchmark results.

Alternatives

ProjectWhat it isPick it when
zkA command-line assistant for a plain-text Zettelkasten or personal wiki.Choose zk for templates, linked-note search and integration with an existing editor. Its README says it is not a note editor; equivalent prediction settlement is not established by the supplied evidence.
SilverBulletA browser-based Markdown editor programmable with Lua, with wiki links, a database and queries.Choose SilverBullet when you want a programmable browser workspace. Do not assume equivalent forecasting features or automatic migration from YOINK.

What people are saying

  1. [velocity-scout] DefiLeoo/YOINK

Sources

  1. YOINK README
  2. YOINK package manifest
  3. YOINK claims documentation
  4. YOINK scoring documentation
  5. README animation issue 1

More dev tools reviews