Assemblyline-service-characterize
Characterize is an add-on for the Assemblyline security system.
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.
35/100 Low
- Maintained
- 68last commit 72 days ago
- Popular
- 61 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 108 GB minimum RAM
- GitHub stars
- 1
- Open issues
- 3
- Last commit
- 2026-09-10
- Latest release
- v4.8.0.stable0
- Activity
- stale
Checked 2 days ago - source: GitHub (CybercentreCanada/assemblyline-service-characterize)
Resources & Compatibility
Minimum requirements: 8 GB RAM, 4 CPU core(s). ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Running within Assemblyline Characterize is an Assemblyline service intended to run inside the Assemblyline framework. You can test it standalone by running its Docker image directly in a shell, or add it to your Assemblyline deployment using the Assemblyline service management guide. source
Fetched 42 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Can I test Characterize without a full Assemblyline deployment?
Yes, run the Docker image directly from a shell with the SERVICE_API_HOST environment variable set to the Assemblyline service API address on port 5003 and the host network.
Which Docker tag should I choose for Characterize updates?
Use the stable tag for the latest stable build and the dev tag for the latest unstable build; latest can be unstable.
What file must exist for the Assemblyline core to run the Characterize service?
Every Assemblyline service must have a service_manifest.yml file in its root directory, and the core needs that manifest before running the service.
Answers sourced from cybercentrecanada.github.io, github.com
Community
Collected 47 days ago - public community threads