⬤  v0.3.3 — MISRA C:2023 · CERT C · CWE

Catch MISRA, CERT C & CWE defects
in C — fully local.

Provadyne runs the latest C coding-standard checks on your own machine — with AI-suggested fixes, SARIF for GitHub code scanning, and reports to support your audit evidence. No cloud upload. No procurement cycle.

Built on cppcheck 2.20  ·  runs 100% offline  ·  BYOK OpenAI / Anthropic / Ollama
Detects MISRA C:2023 SEI CERT C CWE Integrates SARIF · GitHub code scanning ISO 26262-6 traceability
How it works

Three steps, all on your machine.

No agents to install on a build server, no code leaving your network.

01

Install

One binary, no daemon farm.
brew install sgchoi/tap/provadyne-daemon — or grab the release for macOS, Linux, or Windows.

02

Analyze

In your editor, inline on GitHub PRs, or in CI. Pick any mix of MISRA C:2023, CERT C, and CWE per run.

03

Fix & prove

Apply AI-suggested fixes, upload SARIF to code scanning, and export PDF / CSV reports to support your audit evidence.

What's in the box

Latest-spec static analysis, built for embedded C.

Powered by widely-used open source (cppcheck, clang-tidy, clippy). No telemetry, no SaaS lock-in.

Multi-standard detection

MISRA C:2023, SEI CERT C, and CWE in a single local pass — every finding tagged with its standard and CWE id so you filter by what your program requires.

AI fix suggestions

One-click diff previews for each violation. Bring your own key (OpenAI / Anthropic) or run fully offline with a local Ollama model.

SARIF & code scanning New

Emit SARIF 2.1.0 and upload it to GitHub code scanning — violations show up inline on the PR and under the Security tab, CWEs included.

Batch violation reports

Turn a directory of .c files into a batch PDF with severity rollups and per-file rule citations — plus a MISRA Compliance:2020 deviation register (HTML / PDF) built straight from your in-code waivers. CSV / Excel export included. Pro

ISO 26262 traceability

Link Git history to ALM tickets (Codebeamer, Jira) and build a V-model requirement → code → test matrix — coverage traceability to support your ISO 26262 work-product evidence. Pro

100% local & air-gapped

The daemon runs on localhost and works with no network at all. Your source never leaves the machine unless you opt into a BYOK API key.

In your pipeline

Gate every PR — and feed code scanning.

Drop the GitHub Action into a workflow. It installs the engine, runs the checks, fails on the severity you choose, and uploads SARIF.

  • Native GitHub Action (composite, no Docker)
  • SARIF upload → inline PR annotations + Security tab
  • fail-on gate: mandatory / required / advisory / none
  • Same engine as the desktop app — reproducible results
.github/workflows/misra.yml
# Detect, then upload to code scanning
jobs:
  misra:
    runs-on: ubuntu-latest
    permissions:
      security-events: write
    steps:
      - uses: actions/checkout@v4
      - id: scan
        uses: sgchoi/provadyne-action@v1
        with:
          paths: 'src/**/*.c'
          output-format: sarif
      - uses: github/codeql-action/upload-sarif@v3
        with:
          sarif_file: ${{ steps.scan.outputs.sarif-path }}
Editions

Engineer-friendly. Under the corp-card limit.

No seat counting, no procurement cycle. Pay by card; get a license file by email in minutes.

Free

$0 / forever
  • MISRA C:2023 single-file analysis
  • CERT C & CWE detection
  • SARIF output
  • AI fix suggestions (BYOK)
  • Local LLM via Ollama
Download

Team & EnterpriseEarly access

Shared governance, tool-qualification support and on-prem licensing for safety teams — in active development. Join the waitlist to help shape the roadmap and get early access.

Join the waitlist
FAQ

Common questions

Does my code leave my machine?
No. The daemon runs on localhost and analysis is fully local. Nothing is uploaded unless you explicitly enable a BYOK API key for AI suggestions — and even then only the relevant snippet is sent to your chosen provider.
Which standards are supported?
For C: MISRA C:2023, SEI CERT C, and CWE — pick any combination per run. Detection is powered by cppcheck. MISRA C++:2023 and AUTOSAR C++ are on the Phase B roadmap.
Can I run it fully offline / air-gapped?
Yes. Use local LLM mode with Ollama, or disable AI suggestions entirely. The daemon needs no network; the optional update check silently skips when offline.
What is the ISO 26262-6 traceability matrix?
A Pro feature that links your Git history to ALM tickets (Codebeamer, Jira) and builds a V-model requirement → design → code → test trace — coverage traceability to support your ISO 26262 work-product evidence. It runs locally against your repo; nothing is uploaded.
How does it fit into CI?
A native GitHub Action runs the same engine, fails the job on the severity you choose, and can emit SARIF for upload to GitHub code scanning. See the snippet above.
Which platforms are supported?
The daemon ships as a single binary for macOS (arm64 + amd64), Linux (amd64), and Windows (amd64). The editor and browser integrations work anywhere Chrome or VS Code runs.
Who is responsible for compliance?
Provadyne provides static analysis and qualification-support evidence to assist your functional-safety process. Responsibility for ISO 26262 compliance, tool qualification in your specific context, and final product safety remains with you, the user. See our Terms.

Catch MISRA, CERT C & CWE defects early — fully local.

Free for single-file analysis. Runs on your laptop in minutes.