Assemblyline Service Server
Assemblyline Service Server is the required API that segregated Assemblyline 4 services call to receive tasks and publish results to the core system, as they…
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
11/100 Low
- Maintained
- 0GitHub repository is archived
- Popular
- 176 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 108 GB minimum RAM
- GitHub stars
- 6
- Open issues
- 0
- Last commit
- 2026-01-07
- Latest release
- v4.0.0.stable60
- License
- MIT
- Activity
- stale
Checked 2 days ago - source: GitHub (CybercentreCanada/assemblyline-service-server)
Resources & Compatibility
Minimum requirements: 8 GB RAM, 2 CPU core(s), 40 GB disk. ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Running custom services Assemblyline services run in Docker containers and must be built from the cccs/assemblyline-v4-service-base:stable base image; configure each service through service parameters and service variables rather than editing files directly. source
- Repository status The standalone repository is archived — the service server is a component of the Assemblyline 4 malware-analysis suite. Deploy it via the official cccs Docker images and do not expect independent releases from this repo. source
- Assemblyline dependency Use it as part of an Assemblyline 4 deployment; it is the only interface services have to the system. source
- Archived repository status The Assemblyline 4 service server is an internal, segregated-API component that remains part of the Assemblyline 4 core platform in ongoing releases; this standalone GitHub repository is archived because it is maintained under the main Assemblyline platform rather than deprecated. source
Fetched 15 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Can Assemblyline services access other system components directly?
No. The service server is the only interface the services have to the system because they are completely segregated from the other components.
How should I start the service-server Docker image for a stable build?
Use docker run --name service-server cccs/assemblyline-service-server. For a stable build, use the stable build type or a series tag such as 4.5.stable; latest can be unstable and dev is the latest unstable build.
How do I test a service before using it live in Assemblyline?
Use standalone mode via run_service_once to catch bugs. Live mode hooks the service to a development instance so you can debug it and send files to it.
Answers sourced from cybercentrecanada.github.io, github.com
Community
- How do you guys handle server automation? : r/selfhosted - Reddit (reddit)
- self-hosted VirusTotal-like running in a Docker - Reddit (reddit)
Collected 47 days ago - public community threads