GitHub Integration · Powered by Fencia API

Compliance scan
in every pull request

Add the Fencia GitHub Action to your CI/CD pipeline. Every time a PR changes a policy document, technical spec or AI system documentation, Fencia scans it for EU AI Act and GDPR gaps — and posts article-level findings directly on the PR.

Requires Business or Enterprise plan · API access enabled in Dashboard → Settings

Scan on every PR

Automatically scans changed compliance documents every time a pull request is opened or updated. No manual triggers needed.

Article-level findings as PR comments

Findings posted directly on the PR: severity, exact EU AI Act / GDPR article, evidence excerpt from the document, and a fix recommendation.

Fail CI on critical gaps

If any document scores below 60 (critical), the check fails. Teams can fix compliance gaps before they merge — not after an audit.

3-minute integration

One workflow YAML file. One repository secret. Works on any GitHub repository, public or private.

Supports PDF, DOCX, Markdown, TXT

Scan technical specifications, privacy policies, AI system documentation, model cards — whatever your team versions in Git.

Available on Business and Enterprise

Uses the Fencia REST API (Business+ plans). The same units quota you use for manual scans — all deducted atomically with automatic refunds on failure.

.github/workflows/compliance.yml
name: Compliance Check

on:
  pull_request:
    paths:
      - "docs/**"
      - "policies/**"
      - "**/*.pdf"
      - "**/*.md"

jobs:
  fencia-scan:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Fencia Compliance Scan
        uses: fencia-co/fencia-compliance-action@v1
        with:
          api_key: ${{ secrets.FENCIA_API_KEY }}
          fail_on_critical: "true"
          paths: "docs/**/*.pdf,docs/**/*.md,policies/**"
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

How it works

01

Add the workflow

Copy the YAML above into .github/workflows/. Add your FENCIA_API_KEY as a repository secret.

02

Open a pull request

Whenever a PR changes a matching file, the action runs automatically. No manual trigger needed.

03

Review findings on the PR

Article-level findings appear as a comment. Fix gaps before merging. CI fails on critical scores if configured.

Ready to add compliance to your pipeline?

Generate your API key in the dashboard, add one workflow file, and your team will never miss a compliance gap in a PR again.