Anchore Enterprise vs ScanCode.io

Anchore Enterprise is an SBOM-powered platform for continuous software supply-chain security and compliance. It generates software bills of materials for containers, source code, and filesystems in Syft, CycloneDX, and SPDX formats, then continuously scans those SBOMs for vulnerabilities, secrets, and malware. Policy packs cover NIST, FedRAMP, and DISA, while policy-as-code rules use JSON instructions that can be version controlled in Git. Runtime inventory can cover images running across EKS, ECS, AKE, GKE, and OpenShift clusters. Deployment options include an AWS machine image or container images installed with Helm on Kubernetes-compatible platforms, including air-gapped environments. Every feature and operation can be instrumented through an API. Integrations include major CI, registry, and cloud services such as GitHub Actions, GitLab CI, Jenkins, Amazon ECR, Azure DevOps, Docker Hub, and Harbor. It supports API, Linux, self-hosted, and web environments. Pricing is on request; there is no free plan, but a free trial is available.

ScanCode.io provides a web interface and API for running software composition analysis scans in scripted pipelines. It scans containers, Docker images, package archives, and manifests for license, copyright, source, and vulnerability information, and can generate or consume CycloneDX and SPDX SBOMs. The same capabilities are available through its command-line interface and REST API. Documented pipeline integrations include GitHub Actions, Jenkins, GitLab, and Azure Pipelines; other CI/CD systems that support Docker can run it too. It can fetch packages using Package URLs and retrieve artifacts from JFrog Artifactory and Sonatype Nexus. Installation is preferably through Docker, including for Windows; Linux server installation is also supported, and an offline Docker package can be transferred to an isolated server. The software is open source under Apache License 2.0 and is free. Authentication for the web interface and API is disabled by default, but can be enabled. Its default setup starts one worker, so it runs one pipeline at a time.