mrkeyoor.comAsk

FBddcz/embodied-jevtested 07 Oct 2026commit f08de2e

embodied-jev review

Try EmbodiedJev to inspect bounded model decisions in simulation if you can follow its Chinese guides.

  • Build 10 s
24 sto install
  • 26 packages
AI Toolsevaluationupdated 01 Nov 2026
+3stars / 7d

Use EmbodiedJev if you want to inspect model decisions in simulated manipulation and can follow Chinese technical guides. EmbodiedJev is a browser workbench that uses MuJoCo to simulate a Franka Panda arm. Our run checked npm installation and the front-end build; it did not validate a working simulator session.

Verdict

Try EmbodiedJev to inspect bounded model decisions in simulation if you can follow its Chinese guides. Our run on October 7, 2026, at commit f08de2e recorded npm installation in 24 seconds and a front-end build in 10 seconds; both succeeded, and tests were skipped. Before relying on it, verify the Python service, complete a rule-baseline task and run the relevant named suites. Our run provides no simulator or hardware validation, and the conflicting audit outputs remain unresolved.

We ran it

Lab card: what happened when we ran embodied-jev
Lab card from our sandbox run
Screenshot of embodied-jev (github.com/FBddcz/embodied-jev)
github.com/FBddcz/embodied-jev
Install✓ · 24s26 packages · 148 MB
Build✓ · 10s
Testsn/ano test script
Known vulns00 critical · 0 high · 0 moderate · 0 low (npm audit)
Repo344 files~22,258 lines of source · 109.9 MB · 2 CI workflows · tests dir

Answers from our run

Does embodied-jev build from source?

Dependencies installed in 24 seconds (26 packages), and the build succeeded in 10 seconds. We cloned commit f08de2e into a clean Debian container with 3 CPUs and no project-specific setup.

Does embodied-jev have tests you can run?

Not through a standard command: the project exposes no test script or target that our harness could run.

Does embodied-jev have known vulnerabilities in its dependencies?

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

Who should not use embodied-jev?

Teams seeking demonstrated real-robot deployment: the README describes Piper hardware work as a proposal without executed robot actions.

What are the alternatives to embodied-jev?

robosuite, Meta-World. Try EmbodiedJev to inspect bounded model decisions in simulation if you can follow its Chinese guides.

Setup3/5Under the visible rubric, npm installation and build provide useful foundations, but Python installation, service startup and simulator operation were not tested.
Docs4/5Under the visible rubric, the Chinese README and technical guide explain setup, protocols and limitations in detail; English onboarding requires translation.
Community3/5Under the visible rubric, documented contribution and reproduction paths provide useful foundations. This narrow assessment does not measure adoption, responsiveness or support capacity.
Maturity3/5Under the visible rubric, two detected workflows and test directories provide useful foundations, but tests were skipped and our build did not validate application behavior.

Who it’s for

Robotics learners comfortable with Chinese documentation who want to inspect actions, feedback and trajectories in a browser.
Researchers comparing bounded model choices with a rule baseline while keeping task, seed, controller and input mode consistent.
Developers prepared to install the Python service as well as the JavaScript front end and verify the complete application themselves.

Who it’s NOT for

Teams seeking demonstrated real-robot deployment: the README describes Piper hardware work as a proposal without executed robot actions.
Readers who need our run to establish simulator, browser-flow or provider reliability: those workloads were not tested.
Users expecting arbitrary robots or tasks through configuration alone: new robots, actions and success conditions require code changes.
Users seeking a small local-model installation: the documented MiniCPM route downloads about 5 GB of weights and needs further runtime memory.
Experiments whose observations must remain on the machine while using cloud vision: direct-image mode sends enabled camera RGB frames to the provider.

Setup reality

Our run on October 7, 2026, at commit f08de2e recorded npm installation in 24 seconds and a front-end build in 10 seconds; both succeeded, and tests were skipped. These observations come from our Node 22 sandbox with 3 CPUs and 8 GB RAM. The harness records each command's success flag, exit code, elapsed time, timeout flag and retained output tail. Installation and build returned exit code 0 without timing out; the test step records the reason "no script".

The attached stored parser summaries record 26 dependency packages and a 148 MB footprint. The raw installation tail reports a different number of added packages. Those outputs have not been reconciled, so we retain the stored measurements without presenting them as verified package coverage.

The stored audit summary records zero advisories, while the raw installation tail reports one high-severity vulnerability. The evidence does not resolve that disagreement. Scan coverage is unknown because scannedPackages is absent. Neither output proves security.

The documented application setup also needs Python 3.11 or newer, Node.js 22.12 or newer, an editable Python installation, built web assets and the local service. Our run did not verify that complete setup.

What our run established

Our run on October 7, 2026, at commit f08de2e recorded npm installation in 24 seconds and a front-end build in 10 seconds; both succeeded, and tests were skipped.

These are observations from our sandbox. The matching harness stores command outcomes separately from retained log tails: both commands returned exit code 0, neither timed out, and the test step records a skip because there was no default script. A skipped test step is not a failed suite. The successful build establishes that the front-end assets compiled in this environment.

We did not install the Python package, start the service, open the browser interface, execute a MuJoCo task, load MiniCPM or call a model provider. The manifest defines separate UI and site test commands, and the technical guide documents Python tests; our run did not execute them. The raw build output also contains a chunk-size warning despite its successful exit.

The MrKeyoor testing methodology explains how command outcomes and measurement limits reach these reviews. Its supplied October 31 description provides provenance context, not proof that the same methodology version governed our October 7 run. This correction includes no new execution.

What the model controls

EmbodiedJev is a browser workbench that uses MuJoCo to simulate a Franka Panda arm. Its technical guide assigns display and controls to the browser, with physics, model requests and experiment records handled by Python.

The built-in Panda tasks cover moving a block into a tray, stacking it on a fixed block and carrying it over an obstacle. Models select skills or short XYZ and gripper actions, depending on the mode. Program logic handles action conversion, inverse kinematics, execution checks and physical success conditions. The guide says collision monitoring is incomplete and the end-effector orientation is fixed. These are documented capabilities and limits, not behavior we reproduced.

Which comparisons are meaningful

Simulator coordinates, locally detected RGB-D coordinates and raw camera images give models different information. The README separates these inputs and distinguishes prepared-skill selection from incremental movement decisions. Keep those protocols separate when interpreting results: selecting a skill from coordinates answers a different question from choosing movements from images.

The documented comparison interface runs configurations with a shared task and seed and aligns trajectories by simulation time. Replay speed does not establish inference latency because model waiting time is separate. Preserve input mode, controller, seed, action budget and actual elapsed time alongside exported results. The authors' experiment results are not our passing-test counts or independent reproductions.

What to verify after building

Start with the rule baseline, which the documentation says needs no API key, GPU or model weights after installation. Start the Python service, open the local browser page and complete a baseline task before adding a model connection. That checks the application path our npm run left untested.

The supplied Chinese README and technical guide describe setup, protocols and limitations in detail. Windows launch commands are provided, but the README identifies macOS and Linux CI as validated environments. MiniCPM adds optional Python dependencies, about 5 GB of initial weights and further runtime memory. Cloud routes require provider credentials; connection tests and experiments make real requests and may incur charges.

Cloud calls send task state, and direct-image mode also sends enabled cameras' RGB frames. Localhost binding does not prevent that transmission. Decide whether the observations may leave the machine before testing a provider connection.

Why the audit result remains unresolved

The stored audit summary records zero advisories, while the raw installation tail reports one high-severity vulnerability. We cannot reconcile those outputs from the supplied record and do not describe the installation as vulnerability-free. Scan coverage is unknown because the record has no scannedPackages field.

The attached stored parser summaries also record 26 dependency packages and a 148 MB footprint, while the installation tail reports a different added-package count. We preserve the stored values without treating the tail as a replacement measurement. No complete-log reconciliation was supplied, and no test total exists because tests were skipped.

When another project fits

robosuite is a MuJoCo simulation framework for robot learning with benchmark environments for reproducible research. Its primary repository describes modular APIs for environments, robot embodiments and controllers. Choose it when building those simulation components is your main task.

Meta-World is a benchmark for developing and evaluating multi-task and meta reinforcement learning algorithms for robotic manipulation. Its primary repository documents the benchmark environments and Gymnasium interface. Choose it for that evaluation role. EmbodiedJev also reports Meta-World experiments, so the benchmark can complement the workbench rather than replace its browser interface.

How to read the ratings

The editorial rubric runs from 1 to 5: 1 indicates substantial obstacles, 2 substantial gaps with a usable path, 3 useful foundations with material limits, 4 detailed support with a bounded shortcoming, and 5 strong evidence across the dimension. These ratings are judgments about the supplied evidence, not performance measurements.

Setup ease is 3 because npm installation and build succeeded but the Python service and simulator remain unverified. Documentation is 4 for detailed setup and limitation explanations, with Chinese onboarding as a constraint. Community is 3 only for documented contribution and reproduction paths; it does not establish adoption or maintainer responsiveness. Maturity is 3 for detected workflows and test directories, qualified by skipped tests and the narrow build check.

Alternatives

ProjectWhat it isPick it when
robosuiteA MuJoCo simulation framework with robot-learning benchmark environments and modular environment, robot and controller APIs.Choose it when you need to build or modify simulation environments and controllers.
Meta-WorldA benchmark for multi-task and meta reinforcement learning in robotic manipulation.Choose it for those learning benchmarks and their Gymnasium interface. It can complement EmbodiedJev, whose README also reports Meta-World experiments.

What people are saying

  1. [velocity-scout] FBddcz/embodied-jev

Sources

  1. EmbodiedJev README at commit f08de2e
  2. EmbodiedJev technical guide at commit f08de2e
  3. EmbodiedJev package manifest at commit f08de2e
  4. Open localhost setup issue
  5. Open token-accounting issue

More ai tools reviews