AADSec
Home

Known limitations

Version of 28 October 2026. Platform statuses (macOS, Linux, arm64) are published with each version in the release notes.

  • Platform status (v0.1.1): macOS (Intel, macOS 15): tested with 0.1.1. Apple Silicon (darwin_arm64): install and aadsec --version verified on a macOS arm64 runner (CI run 40054317431); scan not tested on Apple Silicon. Linux x86_64: tested under WSL2 (Ubuntu 24.04) with Docker Desktop and natively on GitHub Actions ubuntu-24.04 (CI runs 40054317431 and 40056271929). Linux arm64: CLI and runner image tested natively on GitHub Actions ubuntu-24.04-arm (CI runs 40054317431 and 40056271929). Windows 11: experimental; native folder scans passed in tests with 0.1.0 and were not repeated with 0.1.1; --image and output on /mnt/c under WSL are not supported.
  • Windows is experimental: folder scans work in the tested conditions. The --image option is not supported on Windows, nor is output on /mnt/c under WSL (use /home).
  • If Docker is missing, the message says Docker Desktop is not running: it is misleading in that case.
  • Interrupting the Docker client during a scan can leave a container running; remove it with docker rm -f.
  • The Windows binary has no digital signature: a SmartScreen warning is possible.
  • Evaluation cap: 3 successful scans per machine.
  • The LICENSE, SECURITY and THIRD_PARTY_NOTICES files bundled in 0.1.x archives accompany the evaluation version; the terms published on aadsec.xyz/terms prevail.
  • The runner image embeds Gitleaks 8.30.1: 36 HIGH or CRITICAL findings (including 1 CRITICAL) come from this upstream binary and will be addressed in a later image update.
  • The Trivy vulnerability database in use can differ from the one in the image; its date appears in the report. During the first online scan, AADSec downloads Trivy's vulnerability database into its local cache (about 1.6 GB measured on macOS); --offline uses the database from the image or the cache. The number of Trivy findings depends on the database in use: the totals in the sample report correspond to the database dated 26 October 2026 and may differ with a more recent database.
  • SHA-256 sums are integrity checksums, not signatures; SHA256SUMS does not cover the SBOM or the install scripts.