JKVideo
高颜值第三方 B 站 React Native 客户端
Could not verifysource: GitHubTypeScriptMITcommit 3592d036b193
TypeScript, MIT licensed. The project labels itself: android, danmaku, dash, expo, react native, typescript, video player and zustand.
Argusic could not get JKVideo running. An Argusic agent installed it in 18.5 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install completes, TypeScript compiles with zero errors, and 'npx expo export --platform web' produces a working web build at web-build/ that serves index.html (200) and the 2MB entry JS bundle (200).
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 80 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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- TypeScript errors in 8 files: fontWeight type, Image pointerEvents, FileSystem.getInfoAsync size option type deprecated, undefined vs null mismatch, react-native-video shim event handler signatures4 minutes
- Node.js v18 is too old for React Native 0.83 / Expo SDK 55 (requires >=20.19.4)2.1 minutes
- Expo export fails on Node 18 with 'parseEnv is not a function'1.5 minutes
- shims/sentry-react-native.web.tsx: generic <T> interpreted as JSX tag in TSX, TS17008/TS1382 errors0.5 minutes
- Install time
- 18 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- Web export built: 'npx expo export --platform web --output-dir web-build' exited 0, produced 2MB entry bundle. Static server: index.html 200 (1213 bytes), entry.js 200 (1,975,011 bytes). TypeScript: 'npx tsc --noEmit' exited 0 with zero errors.
- Model tokens used
- 131,278
- Exact commit tested
- 3592d036b193
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- **Serving** the build: `index.html` → 200 (1213 bytes), `entry.js` → 200 (1,975,011 bytes), `favi… - **Proxy server** `node dev-proxy.js` starts and listens on port 3001 No test suite exists in the project, so test_depth is tier3_none. No third-party credentials were n… tokens used 131,278 Everything is verified. Let me compile the final report: - **`npm install`** succeeded (773 packages, exit 0) - **TypeScript** compiles with zero errors after fixing `shims/sentry-react-native.web.tsx` (JSX ge… - **Web export** (`npx expo export --platform web`) produces a 2MB entry bundle - **Serving** the build: `index.html` → 200 (1213 bytes), `entry.js` → 200 (1,975,011 bytes), `favi… - **Proxy server** `node dev-proxy.js` starts and listens on port 3001 No test suite exists in the project, so test_depth is tier3_none. No third-party credentials were n…
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
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- 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
- An agent with no time limit did not get it running.
- Took 18.5 minutes to install, slower than the median of the 12 comparable projects Argusic has measured.
Of the 13 android projects Argusic has installed and timed, JKVideo was the 11th fastest to reach a running state, and 10 of 13 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Unverified | 80.00 | 0.05 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.03 |
Topics (from GitHub)
androiddanmakudashexporeact-nativetypescriptvideo-playerzustand
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/jkvideo)Questions
- Does JKVideo run?
- Argusic could not verify that JKVideo runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test JKVideo?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3592d036b193. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test JKVideo?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does JKVideo take to install?
- 18.5 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 JKVideo need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing JKVideo?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does JKVideo compare with the alternatives?
- Of the 13 android projects Argusic has installed and timed, JKVideo was the 11th fastest to reach a running state, and 10 of 13 reached one at all.
- Where is the evidence for JKVideo?
- 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.