DRIFTSEAL/ 01bymAIb
TECHNICAL NOTES / V0.1

GitHub Action

Static checks and baseline comparison inside CI. No cloud signup required.

Add it to a workflow

Save the workflow below as .github/workflows/driftseal.yml and point path at your tool/skill directory or JSON manifest. The Action sets up Python 3.12 and works without cloud signup. Pin a reviewed commit for stronger provenance.

name: DriftSeal
on: [pull_request, push]
jobs:
  driftseal:
    runs-on: ubuntu-latest
    permissions:
      contents: read
    steps:
      - uses: actions/checkout@v4
      - uses: mAIb-Tech-LLC/driftseal@v1
        id: driftseal
        with:
          path: ./agent-tools
          baseline: .driftseal-baseline.json
          fail-on: critical
      - uses: actions/upload-artifact@v4
        if: always()
        with:
          name: driftseal-evidence
          path: ${{ runner.temp }}/driftseal-results/

Approve a baseline

Create a baseline locally and commit it after review. If the baseline file exists, the Action compares against it. If absent, it reports static indicators from a one-time scan. Baseline target identities must match.

Want to know when this changes later?

A point-in-time Action run is not continuous monitoring. Open https://drift.maib.io/?source=github-action#scanner, scan a public component and choose WATCH THIS COMPONENT. Paid monitoring checks it between commits; private repositories remain local.

Optional stage measurement

Telemetry is disabled by default. Set telemetry: true to report a fresh random run ID and whether a baseline was compared. An optional installation-id must be a random UUID. No repository name, target coordinate, source, filenames or findings are sent. These opt-in reports are not treated as verified customers or verified installations.

Results and permissions

The Action writes a job summary, report.json, result.json and result.sarif. It sets result and sarif outputs. Upload SARIF with GitHub's supported code-scanning upload action when the repository supports it and grants security-events: write. Uploading artifacts with if: always() preserves results when severity gating fails.

The Action does not post PR comments or request write access by default. It does not install the target project. Untrusted pull requests must not receive cloud tokens. Do not use pull_request_target to execute unreviewed PR code.

Establish your baseline.

Inspect a public component or use the local CLI for private source.

Scan a component — free ↗
YOUR TRUST LEDGER

Keep watch.

Sign in with a one-time email link. No password to remember.