sharing
Sharing is a command-line tool to share directories and files from the CLI to iOS and Android devices without the need of an extra client app
Runssource: GitHubJavaScriptMITcommit e103cc312422
JavaScript, MIT licensed. The project labels itself: android, browser, cli app, clipboard share, command line tool, filesharing, filesharing on network and filetransfer.
sharing runs. An Argusic agent installed it in 1 minute and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The easy-sharing 1.4.0 project installs cleanly, all 32 tests pass, the CLI correctly prints version and help, and the HTTP file-sharing server starts on a specified port, serves directory listings and files, and renders the QR page, all verified via HTTP requests returning 200 with correct content.
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
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
- 1 minutes
- Cold machine to finish
- 1 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- npm test exited 0, 32 passed 0 failed; curl -s -o /dev/null -w '%{http_code}' http://localhost:9877/share/ returned 200; curl -s http://localhost:9877/share/test.txt returned 'hello world'; curl -s http://localhost:9877/qr returned 200; node bin/index.js --version returned '1.4.0'
- Model tokens used
- 14,372
- Exact commit tested
- e103cc312422
- 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.
**Errors:** None encountered throughout the entire process. tokens used 14,372 Here's the final assessment. **Install:** `npm install` completed, 231 packages installed. No build step needed. **Tests:** `npm test` — 32 passed, 0 failed. **CLI verification:** - `--version` printed `1.4.0` - `--help` printed full usage screen - Server started on port 9877 and served directory listing (HTTP 200 at `/share/`), file content (`… **Global install:** Not possible in this container (EACCES on `/usr/local/lib`), but `npx easy-shar… **Errors:** None encountered throughout the entire process.
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.
- Installed in 1 minute, faster than the median of the 29 comparable projects Argusic has measured.
- 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.
- Measured 2 times, so the result is not a one-off.
Of the 30 android projects Argusic has installed and timed, sharing was the 7th fastest to reach a running state, and 23 of 30 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 1 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
Topics (from GitHub)
androidbrowsercli-appclipboard-sharecommand-line-toolfilesharingfilesharing-on-networkfiletransferioslinuxnodejsqrcodereceive-filesserving-directoryutility
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/sharing)Questions
- Does sharing run?
- Yes. sharing runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test sharing?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e103cc312422. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test sharing?
- 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 sharing take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does sharing need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing sharing?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does sharing compare with the alternatives?
- Of the 30 android projects Argusic has installed and timed, sharing was the 7th fastest to reach a running state, and 23 of 30 reached one at all.
- Where is the evidence for sharing?
- 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.