Integrate Endor Labs with Vulnesis. Use endorctl to scan dependencies with reachability analysis, export SARIF findings, and upload to Vulnesis for centralised risk management.
Run Endor Labs in CI
Scan on every push and upload the report as a workflow artifact:
- name: Install endorctl
run: |
curl -s https://api.endorlabs.com/download/latest/endorctl_linux_amd64 -o endorctl && chmod +x endorctl
- name: Endor Labs scan
run: |
./endorctl scan --namespace ${{ secrets.ENDOR_NAMESPACE }} --as-default-branch
./endorctl api get-vulnerabilities --namespace ${{ secrets.ENDOR_NAMESPACE }} --sarif > endorlabs.sarif
env:
ENDOR_API_CREDENTIALS_KEY: ${{ secrets.ENDOR_API_KEY }}
- name: Upload report
uses: actions/upload-artifact@v6
with:
name: endorlabs
path: endorlabs.sarif
if-no-files-found: warnThen one publish job hands every artifact in the run to Vulnesis, recorded under Endor Labs's own name and version. Written once per workflow, however many scanners you run:
publish:
name: Publish to Vulnesis
runs-on: ubuntu-latest
needs: [scan] # every scanner job, or its report is never published
if: always() # or one failing scanner suppresses all the others
permissions:
contents: read
actions: read # required to list the run's artifacts
env:
VULNETIX_ORG_ID: ${{ secrets.VULNETIX_ORG_ID }}
VULNETIX_API_KEY: ${{ secrets.VULNETIX_API_KEY }}
steps:
- uses: actions/checkout@v5
- name: Install Vulnesis CLI
run: |
curl -fsSL https://cli.vulnes.is/install.sh | sh -s -- --install-dir "$HOME/.local/bin"
echo "$HOME/.local/bin" >> "$GITHUB_PATH"
- name: Publish scanner reports
env:
GITHUB_TOKEN: ${{ github.token }}
run: vulnetix gha upload --org-id "$VULNETIX_ORG_ID" --jsonAfter the run, vulnetix gha status reports what was actually recorded.
How Vulnesis compares: better together
Vulnesis does not replace Endor Labs. Keep running it. Vulnesis sits on top of Endor Labs (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
Endor Labs is strongest at its core category and also carries features in SAST, Secret Scanning, Container & Image Scanning, SBOM Generation, License Compliance, just as Vulnesis spans categories.
| Capability | Vulnesis | Endor Labs |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✓ Native SAST: rule-based (Opengrep) plus AI SAST scanning code and PRs for code-level flaws |
| SCA / dependencies | ✓ 40+ ecosystems, transitive graph | ✓ Core product: reachability-aware SCA across major ecosystems against OSV/advisory data |
| DAST (dynamic testing) | ~ Ingests DAST results; no native dynamic engine | ✗ |
| Container & image | ✓ Image CVEs, base image, Dockerfile | ✓ Container image scanning, layer-aware, marketed as container + SCA better together |
| IaC / misconfiguration | ✓ Terraform, k8s, CloudFormation | ✗ |
| Secret scanning | ✓ 1,000+ rules, source + binary + git history | ✓ Secret/credential and API-key detection pre-commit, at commit, and in production |
| Cloud / CSPM | ✓ Cloud-posture findings, compliance tab | ✗ |
| Mobile (MAST) | ~ Ingests mobile scanner output; no native mobile engine | ✗ |
| License compliance | ✓ SPDX, copyleft/AGPL/SSPL policy | ~ Detects legal/licensing risk across the SDLC |
| SBOM generation | ✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable | ~ Centralized SBOM creation and management; CycloneDX-oriented, less on generation breadth |
| Malware / supply-chain | ✓ De-duplicated corpus + install-time firewall (25 registries) | ~ Malicious-package detection for supply-chain risk; not an install-time registry firewall |
| 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 Vulnesis orchestration layer | ||
| Cross-scanner dedup & one queue (ASPM) | ✓ Correlates every scanner into one prioritised queue with ownership routing | ~ Unifies code, SCA, container, secrets, malware findings into one platform view |
| Exploit-intel prioritisation | ✓ EPSS, CISA KEV, Coalition ESS, CWSS, Vulnesis LEV | ~ Risk-based prioritisation factors EPSS alongside reachability; not a multi-source exploit-intel engine |
| Reachability analysis | ✓ Tree-sitter + CVEAffected; direct/transitive/semantic | ✓ Function-level call-graph reachability is the flagship capability that suppresses unreachable CVEs |
| Versioned VEX + audit trail | ✓ Immutable OpenVEX/CycloneDX, cosign-signable | ~ Creates and manages VEX; not documented as immutable/versioned with audit trail |
| Safe Harbour autofix | ✓ Resolves + applies the nearest safe version | ~ Automated patching and AI code fixes with upgrade-impact analysis |
| 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 Endor Labs does well
- Function-level reachability analysis that filters out unreachable CVEs, cutting dependency alert noise by a claimed 80-92%
- Unified developer-first platform combining reachability SCA, SAST (rule-based Opengrep plus AI SAST), secrets, container scanning, and malicious-package detection in one product
- Strong remediation focus: upgrade-impact analysis and automated patching so bumps don't break the build
- AI model discovery and governance (finds AI models/usage in codebases) plus centralized SBOM and VEX generation
Where Vulnesis adds to it: Both center on reachability, but Vulnesis is an orchestration/ASPM layer that ingests and dedupes findings from Endor Labs alongside other scanners into one prioritised queue, adds broader exploit-intel (EPSS, CISA KEV, Coalition ESS, CWSS, LEV) and SSVC policy, immutable versioned VEX with audit, EOL policy, and an install-time package firewall across 25+ registries. Vulnesis layers on top of Endor Labs rather than replacing its function-level reachability engine.
No migration, no rip-and-replace. Endor Labs keeps doing what it does best; Vulnesis adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today. Software Factory agents on a Pix Sandbox can then turn the findings from any scanner into pull requests that a person approves. How Software Factory works.
Centralise Endor Labs results in Vulnesis
Upload Endor Labs SARIF, CycloneDX output to the Vulnesis 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.