Integrate FOSSology with Vulnetix. Deploy FOSSology via Docker Compose, upload source archives, run licence scans, and export SPDX or CycloneDX SBOMs via the REST API for Vulnetix ingestion.
Install & scan
$ # Docker Compose (recommended)
git clone https://github.com/fossology/fossology
cd fossology
docker compose up -d
# UI available at http://localhost:8081 (fossy/fossy)
$ # Authenticate and get API token
FOSSOLOGY_URL="http://localhost:8081"
TOKEN=$(curl -s -X POST "$FOSSOLOGY_URL/api/v2/tokens" -H "Content-Type: application/json" -d '{"username":"fossy","password":"fossy","token_name":"ci","token_scope":"write","token_expire":"2025-12-31"}' | jq -r '.Authorization')
# Upload source archive
UPLOAD_ID=$(curl -s -X POST "$FOSSOLOGY_URL/api/v2/uploads" -H "Authorization: Bearer $TOKEN" -F "fileInput=@my-project.tar.gz" -F "folderId=1" | jq -r '.message')
echo "Upload ID: $UPLOAD_ID - wait for analysis, then export CycloneDX SBOM"
Run FOSSology in CI
Scan on every push and upload the report as a workflow artifact:
- name: Start FOSSology
run: |
git clone --depth=1 https://github.com/fossology/fossology
cd fossology && docker compose up -d
sleep 30
- name: Upload and scan
run: |
TOKEN=$(curl -s -X POST "http://localhost:8081/api/v2/tokens" -H "Content-Type: application/json" -d '{"username":"fossy","password":"fossy","token_name":"ci","token_scope":"write","token_expire":"2026-01-01"}' | jq -r '.Authorization')
UPLOAD_ID=$(curl -s -X POST "http://localhost:8081/api/v2/uploads" -H "Authorization: Bearer $TOKEN" -F "fileInput=@project.tar.gz" -F "folderId=1" | jq -r '.message')
echo "UPLOAD_ID=$UPLOAD_ID" >> $GITHUB_ENV
How Vulnetix compares: better together
Vulnetix does not replace FOSSology. Keep running it. Vulnetix sits on top of FOSSology (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
FOSSology is strongest at its core category and also carries features in SBOM Generation, Compliance & Policy Engines, just as Vulnetix spans categories.
| Capability | Vulnetix | FOSSology |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✗ |
| SCA / dependencies | ✓ 40+ ecosystems, transitive graph | ~ Scans uploaded source packages for licenses; does not resolve dependency trees or scan for CVEs |
| DAST (dynamic testing) | ~ Ingests DAST results; no native dynamic engine | ✗ |
| Container & image | ✓ Image CVEs, base image, Dockerfile | ✗ |
| IaC / misconfiguration | ✓ Terraform, k8s, CloudFormation | ✗ |
| Secret scanning | ✓ 1,000+ rules, source + binary + git history | ✗ |
| Cloud / CSPM | ✓ Cloud-posture findings, compliance tab | ✗ |
| Mobile (MAST) | ~ Ingests mobile scanner output; no native mobile engine | ✗ |
| License compliance | ✓ SPDX, copyleft/AGPL/SSPL policy | ✓ Core: nomos/monk/ojo scanning agents with a database-backed clearing/review workflow |
| SBOM generation | ✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable | ✓ CycloneDX agent (since 4.4.0) plus SPDX 2.x/3.0 report generation |
| Malware / supply-chain | ✓ De-duplicated corpus + install-time firewall (25+ registries) | ✗ |
| Network / infra vuln | ~ Ingests network scanner output; no native network scanner | ✗ |
| Fuzzing | ✗ Ingests fuzzing crashes; no native fuzzer | ✗ |
| Pentest / bug bounty | ✗ Ingests pentest/bug-bounty findings; not a testing service | ✗ |
| The Vulnetix orchestration layer | ||
| Cross-scanner dedup & one queue (ASPM) | ✓ Correlates every scanner into one prioritised queue with ownership routing | ✗ |
| Exploit-intel prioritisation | ✓ EPSS, CISA KEV, Coalition ESS, CWSS, Vulnetix LEV | ✗ |
| Reachability analysis | ✓ Tree-sitter + CVEAffected; direct/transitive/semantic | ✗ |
| Versioned VEX + audit trail | ✓ Immutable OpenVEX/CycloneDX, cosign-signable | ✗ |
| Safe Harbour autofix | ✓ Resolves + applies the nearest safe version | ✗ |
| End-of-life policy | ✓ Flags/blocks past-EOL runtimes & packages | ✗ |
| SSVC / risk-based policy | ✓ SSVC v2 + CISA/FedRAMP/Essential-8 presets | ✗ |
✓ full · ~ partial · ✗ not covered
What FOSSology does well
- Mature web-based compliance server with an upload/scan/review/clearing workflow and human audit trail
- Multiple complementary license scanning agents (nomos regex, monk, ojo SPDX-ID) plus copyright detection
- Expanded REST API (v1 and v2) covering nearly all UI functions for CI/CD automation
- Broad export: SPDX 2.x/3.0 (JSON, JSON-LD, RDF, tag/value), a CycloneDX agent, and ECC export-control scanning
Where Vulnetix adds to it: FOSSology is a license-compliance and clearing server; Vulnetix ingests its SPDX/CycloneDX exports and layers the vulnerability and supply-chain program on top (exploit-intel, dedup, reachability, VEX, autofix) rather than running its clearing workflow.
No migration, no rip-and-replace. FOSSology keeps doing what it does best; Vulnetix adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today.
Centralise FOSSology results in Vulnetix
Upload FOSSology SPDX, CycloneDX, JSON, CSV output to the Vulnetix platform to deduplicate findings, prioritise them with EPSS, CISA KEV and Coalition ESS exploit intelligence, and track remediation across every scanner in a single queue.