Integrate GoSec with Vulnetix. Scan Go source code for security anti-patterns including SQL injection, command injection, hardcoded credentials, weak cryptography, and insecure TLS settings.
Install & scan
$ go install github.com/securego/gosec/v2/cmd/gosec@latest $ gosec -fmt=sarif -out=gosec.sarif ./...
Run GoSec in CI
Scan on every push and upload the report as a workflow artifact:
- name: Setup Go
uses: actions/setup-go@v6
with:
go-version: stable
- name: Install GoSec
run: go install github.com/securego/gosec/v2/cmd/gosec@latest
- name: Run GoSec
run: gosec -fmt=sarif -out=gosec.sarif ./...
- name: Upload report
uses: actions/upload-artifact@v6
with:
name: gosec
path: gosec.sarif
if-no-files-found: warnThen one publish job hands every artifact in the run to Vulnetix, recorded under GoSec's own name and version. Written once per workflow, however many scanners you run:
publish:
name: Publish to Vulnetix
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 Vulnetix CLI
run: |
curl -fsSL https://cli.vulnetix.com/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 Vulnetix compares: better together
Vulnetix does not replace GoSec. Keep running it. Vulnetix sits on top of GoSec (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
GoSec is strongest at its core category and also carries features in Secret Scanning, just as Vulnetix spans categories.
| Capability | Vulnetix | GoSec |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✓ Core: scans Go AST/SSA with pattern, taint and blocklist rules (G1xx-G7xx) |
| SCA / dependencies | ✓ 40+ ecosystems, transitive graph | ✗ |
| 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 | ~ G101 flags hardcoded credentials in source, but no entropy/multi-format secret engine |
| Cloud / CSPM | ✓ Cloud-posture findings, compliance tab | ✗ |
| Mobile (MAST) | ~ Ingests mobile scanner output; no native mobile engine | ✗ |
| License compliance | ✓ SPDX, copyleft/AGPL/SSPL policy | ✗ |
| SBOM generation | ✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable | ✗ |
| 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 GoSec does well
- Go-native AST + SSA analysis with taint tracking (G701-G706) for SQL/command injection, path traversal, SSRF and SSTI directly on Go source
- Broad rule coverage across credentials, crypto/TLS weakness, file-permission and blocklisted-import categories tuned specifically for idiomatic Go pitfalls
- Rich output-format support (SARIF, JSON, JUnit, SonarQube, CSV) making it trivial to wire into GitHub code scanning and CI gates
- Free, fast, single-binary and zero-config, the de-facto Go security linter
Where Vulnetix adds to it: Vulnetix runs gosec-class SAST natively (built-in rules + Semgrep) but treats gosec as a first-class ingest source: it dedups gosec findings across scanners into one prioritised queue and layers exploit-intel (EPSS/KEV/LEV), reachability, versioned VEX, SSVC and Safe Harbour autofix, none of which gosec provides.
No migration, no rip-and-replace. GoSec keeps doing what it does best; Vulnetix adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today.
Centralise GoSec results in Vulnetix
Upload GoSec SARIF 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.