Skip to content

Releases: aegisgatesecurity/aegisgate-scanner

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 15 Oct 18:33
v0.4.0
d40896d

What's Changed

  • chore(deps): Bump actions/setup-go from 5 to 7 by @dependabot[bot] in #1
  • chore(deps): Bump golang from 1.26.9-bookworm to 1.27.0-bookworm by @dependabot[bot] in #2
  • chore(deps): Bump softprops/action-gh-release from 2 to 3 by @dependabot[bot] in #3
  • chore(deps): Bump trufflesecurity/trufflehog from 3.98.0 to 3.99.2 by @dependabot[bot] in #5
  • chore(deps): Bump docker/setup-qemu-action from 3 to 4 by @dependabot[bot] in #6

New Contributors

Full Changelog: v0.3.0...v0.4.0

v0.3.0 — AI Artifact Static Analysis Scanner

Choose a tag to compare

@jcolvin1056 jcolvin1056 released this 13 Oct 01:15
v0.3.0
4372a07

AegisGate Scanner v0.3.0

Antivirus for AI artifacts. Static analysis that detects prompt injection, PII, secrets, dangerous code, and compliance violations in RAG documents, training data, model configs, and agent skills.

Highlights

  • 268 regex patterns across 9 security categories
  • CharCNN-BiLSTM (v13) ML detection for prompt injection
  • 8 output formats: SARIF, JSON, Text, HTML, PR Comment, GitHub Actions, SBOM, Markdown
  • Three-layer pipeline: regex → ML → heuristic
  • 1.88s/MB with content-hash caching (LRU eviction)
  • Zero external dependencies (air-gapped capable)

Download Binaries

Platform File
Linux amd64 aegisgate-scanner-0.3.0-linux-amd64.tar.gz
Linux arm64 aegisgate-scanner-0.3.0-linux-arm64.tar.gz
macOS Intel aegisgate-scanner-0.3.0-darwin-amd64.tar.gz
macOS Apple Silicon aegisgate-scanner-0.3.0-darwin-arm64.tar.gz

GitHub Action

- uses: aegisgatesecurity/aegisgate-scanner@v0
  with:
    path: '.'
    format: 'sarif'
    severity: 'medium'
SBOM
sbom-cyclonedx.json — CycloneDX 1.6 (48 components)
sbom-spdx.json — SPDX 2.3 (38 packages)
Verify Checksums

sha256sum -c checksums-sha256.txt
US Provisional Patent App. No. 64/174,824


The binaries, checksums, and SBOMs are **already attached** to the v0.3.0 release from our earlier upload — they should appear in the "Attach binaries" section automatically when you select the existing `v0.3.0` tag. If not, just publish the release and the assets will carry over.