remarshal

Convert between CBOR, JSON, MessagePack, TOML, and YAML 1.1 & 1.2

Runssource: GitHubhomepagePythonMITcommit 2300f5dfc394

Python, MIT licensed. The project labels itself: cli, command line tool, conversion, converter, json, messagepack, msgpack and starlark.

remarshal runs. An Argusic agent installed it in 4 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Remarshal 2.1.4 is installed in a Python 3.12 venv; all 196 tests pass; CLI converts between JSON, YAML, TOML, CBOR, MessagePack, and Python without errors.

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 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.00 (measured)
recorded runs
1
last tested
stars
554
forks
37
open issues
5
watchers
6
size
0 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
4 minutes
Cold machine to finish
1 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
pip install -e '.[dev]' exited 0; python -m pytest tests/ -v returned 196 passed in 0.58s; remarshal --version returned 2.1.4; 'echo {"hello":"world"} | remarshal -f json -t yaml' produced hello: world
Model tokens used
25,990
Exact commit tested
2300f5dfc394
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

The end of the recording

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

exec
/bin/sh -lc ". /tmp/remarshal-venv/bin/activate && echo '{\"numbers\":[1,2,3]}' | remarshal -f json…
 succeeded in 16ms:
hello: world
 succeeded in 17ms:
2.1.4
 succeeded in 43ms:
numbers = [1, 2, 3]
Everything works cleanly. Let me compile the final result.
tokens used
25,990
Everything works cleanly. Let me compile the final result.

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

  • Reached a running state on a clean machine, with the session recorded.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Took 4 minutes to install, slower than the median of the 127 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 128 cli projects Argusic has installed and timed, remarshal was the 85th fastest to reach a running state, and 117 of 128 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 4 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

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/3Runs100.000.00

Topics (from GitHub)

clicommand-line-toolconversionconverterjsonmessagepackmsgpackstarlarkstarlark-pythontomlutilityyaml

Embed the badge

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

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

Questions

Does remarshal run?
Yes. remarshal runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test remarshal?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2300f5dfc394. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test remarshal?
The run that produced this verdict cost $0.00: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does remarshal take to install?
4 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 remarshal need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing remarshal?
Nothing did, in the recorded run: zero errors between clone and running.
How does remarshal compare with the alternatives?
Of the 128 cli projects Argusic has installed and timed, remarshal was the 85th fastest to reach a running state, and 117 of 128 reached one at all.
Where is the evidence for remarshal?
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