huawei-cloud-cloudrobo-dataset@1.0.3
CAUTIONPublisher claims: "Manage CloudRobo data processing (proc-tasks) and data evaluation (eval-tasks) — query algorithms, create/list/show/update/delete/copy tasks; poll task status until terminal; retrieve system and job logs; download logs; query task events (normal/warning); preview output data and frames; discover available algorithms from the asset marketplace; orchestrate processing→evaluation pipelines; batch-manage tasks across workspaces; diagnose failures via log analysis; and onboard custom data-processing operators (five-phase: deploy mode → code adaptation → image build/SWR push or OBS delivery → asset registration → runtime verification). Chained evaluation only; standalone simulation evaluation belongs to huawei-cloud-cloudrobo-eval. Multi-stage data-cleaning pipelines belong to huawei-cloud-cloudrobo-data-pipeline. Triggers include: data processing task management, data evaluation task management, task copy, task status polling, task events, log retrieval for troubleshooting, output data preview, algorithm discovery, task pipeline orchestration, batch task management, failure diagnosis, custom operator onboarding, dataset, proc-tasks, eval-tasks. Also prepare LeRobot manifest.yaml from a local ROS2 bag through terminal conversation or the bag2manifest Web workbench. Triggers include bag2manifest, ROS2 bag转LeRobot配置, 对话生成manifest.yaml, 启动bag2manifest Web服务, 话题映射." Observed in sandbox: static analysis only — behavior not yet observed.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-04 and scored it 58/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
What would make this Verified
22 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim huaweicloudskill: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- Destructive file system command detected≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.