Integrate Psalm with Vulnetix. Analyze PHP code for type errors and security issues like tainted data with SARIF output.
Install & scan
$ composer require --dev vimeo/psalm $ ./vendor/bin/psalm --output-format=sarif > psalm.sarif
Run Psalm in CI
Scan on every push and upload the report as a workflow artifact:
- name: Install Psalm
run: composer require --dev vimeo/psalm
- name: Run Psalm
run: ./vendor/bin/psalm --output-format=sarif > psalm.sarif
- name: Upload report
uses: actions/upload-artifact@v6
with:
name: psalm
path: psalm.sarif
if-no-files-found: warnThen one publish job hands every artifact in the run to Vulnetix, recorded under Psalm'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 Psalm. Keep running it. Vulnetix sits on top of Psalm (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
| Capability | Vulnetix | Psalm |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✓ PHP static + taint analysis for SQLi, XSS, command injection, RCE, SSRF, path traversal (psalm.dev security_analysis docs) |
| 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 | ✗ |
| 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 Psalm does well
- Deep PHP-native type inference and flow analysis that catches type errors and dead code without executing the code
- First-class taint analysis (--taint-analysis) tracing user input through the codebase to dangerous sinks (SQLi, XSS, shell/command injection, RCE, SSRF, path traversal, unsafe unserialize)
- Native SARIF output plus taint-graph DOT visualization, with a maintained GitHub Action for code scanning
- Custom taint sources/sinks and baseline support let large legacy PHP codebases adopt it incrementally
Where Vulnetix adds to it: Psalm is a best-in-class PHP-only SAST/taint engine; Vulnetix does not replace it. Vulnetix ingests Psalm's SARIF, dedups its findings across other scanners into one prioritised queue, and layers EPSS/KEV/LEV exploit-intel, reachability, versioned VEX, SSVC and autofix that Psalm has no notion of.
No migration, no rip-and-replace. Psalm keeps doing what it does best; Vulnetix adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today.
Centralise Psalm results in Vulnetix
Upload Psalm 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.