Medical Imaging Suite
v1.0.0Complete medical imaging solution with OHIF viewer, DICOMweb integration, segmentation, and MONAI workflows, deployable via Docker.
⭐ 0· 267·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description promise a complete OHIF + DICOMweb + MONAI workflow deployable via Docker, but the distributed files contain only a short SKILL.md and a deploy.sh that prints messages and refers to other skills (ohif-deploy, dicom-segmentation-api) rather than implementing deployment. The SKILL.md says Docker is required, but the registry metadata lists no required binaries—this mismatch suggests the package is a placeholder or incomplete.
Instruction Scope
Runtime instructions are minimal and limited: they tell the user to run ./deploy.sh (which only echoes messages). There are no commands that read files, access environment variables, or contact external endpoints. The scope is narrow but not delivering the advertised functionality.
Install Mechanism
There is no install spec and no downloads or extracts. Because this is instruction-only with a tiny script that does not write to disk beyond itself, the install mechanism poses minimal risk.
Credentials
The skill declares no required environment variables, credentials, or config paths, and the files do not reference secrets. This is proportionate to the actual (placeholder) content, though it contradicts the SKILL.md requirement of Docker being present.
Persistence & Privilege
The skill does not request persistent always-on inclusion and does not modify other skills or system settings. Default autonomous invocation is allowed (platform default) but not relevant given the skill's minimal behavior.
What to consider before installing
This package appears to be a placeholder/launcher rather than a complete deployment tool. Before installing or running it: 1) don't run it against production or sensitive patient data — test in an isolated environment; 2) verify the existence and trustworthiness of the referenced skills (ohif-deploy, dicom-segmentation-api) — the real deployment appears delegated to them; 3) confirm Docker-related artifacts (Dockerfiles, docker-compose, container images) and inspect those files for unwanted network endpoints or secret usage; 4) check author provenance (no homepage or repo provided) and prefer packages with clear source repositories and documented release artifacts; 5) if you need a production-ready medical imaging stack, require full manifests and security/privacy compliance documentation before use.Like a lobster shell, security has layers — review code before you run it.
latestvk973ekj486yzswb5sw5d8q6ky5828ggn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.