Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
ci: verify full-history secret scans
AkitaOnRails6161986a77cb
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.ymlindex e5c56c9f..ceafe871 100644--- a/.github/workflows/ci.yml+++ b/.github/workflows/ci.yml@@ -202,8 +202,8 @@ jobs:steps:- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1with:- # Full history so the scan covers every commit reachable- # from the pushed ref, not just the last one.+ # The action scans the pushed/PR commit range. Full history is+ # checked separately by secret-scan.yml on a schedule or on demand.fetch-depth: 0- uses: gitleaks/gitleaks-action@e0c47f4f8be36e29cdc102c57e68cb5cbf0e8d1e # v3.0.0env:diff --git a/.github/workflows/secret-scan.yml b/.github/workflows/secret-scan.ymlnew file mode 100644index 00000000..a9ff01d7--- /dev/null+++ b/.github/workflows/secret-scan.yml@@ -0,0 +1,24 @@+name: full-history secret scan++on:+ schedule:+ - cron: "17 3 * * 1"+ workflow_dispatch:++permissions:+ contents: read++jobs:+ gitleaks:+ name: gitleaks (full history)+ runs-on: ubuntu-latest+ steps:+ - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1+ with:+ fetch-depth: 0+ # workflow_dispatch and schedule events make this pinned action scan the+ # complete reachable history. Push/PR scans remain differential in ci.yml.+ - uses: gitleaks/gitleaks-action@e0c47f4f8be36e29cdc102c57e68cb5cbf0e8d1e # v3.0.0+ env:+ GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}+ GITLEAKS_CONFIG: .gitleaks.tomldiff --git a/.gitleaks.toml b/.gitleaks.tomlindex 770975a5..219fbd93 100644--- a/.gitleaks.toml+++ b/.gitleaks.toml@@ -1,13 +1,14 @@# gitleaks configuration for ai-memory.#-# Wired into CI via `.github/workflows/ci.yml`'s `gitleaks` job. Runs-# on every push and PR; fails the build if a credential-shaped value-# lands in any tracked file.+# Wired into CI via `.github/workflows/ci.yml` for changed commits and+# `.github/workflows/secret-scan.yml` for scheduled/manual full-history+# scans. Both fail if a credential-shaped value is not explicitly reviewed.## The default ruleset (Google API keys, Anthropic, OpenAI, Slack, AWS,# GitHub PATs, …) covers what ai-memory's own sanitiser covers. We# inherit it and only ADD an allowlist for the specific test fixtures-# we deliberately ship.+# we deliberately ship. `.gitleaksignore` contains exact fingerprints for+# reviewed legacy findings; never add broad commit, path, or rule exclusions.## Lesson from M18: a previous iteration of sanitize.rs used a live# Gemini key as a test fixture and Google's automated scanner caughtdiff --git a/.gitleaksignore b/.gitleaksignorenew file mode 100644index 00000000..1f3135b9--- /dev/null+++ b/.gitleaksignore@@ -0,0 +1,6 @@+6004869ea350546a8aefcf1237895e708cc51557:crates/ai-memory-cli/src/commands/hook.rs:generic-api-key:389+16e87742aeb51ac34a44f71392b05579865e9b9e:crates/ai-memory-wiki/src/wiki.rs:github-pat:1719+747c32d50f824cae665f2e35bbd62c8502438903:crates/ai-memory-hooks/src/sanitize.rs:generic-api-key:125+747c32d50f824cae665f2e35bbd62c8502438903:crates/ai-memory-hooks/src/sanitize.rs:jwt:107+d8361d3c3a86f870f74841b53c568c64fe42ab1f:crates/ai-memory-core/src/sanitize.rs:gcp-api-key:226+d8361d3c3a86f870f74841b53c568c64fe42ab1f:crates/ai-memory-core/src/sanitize.rs:generic-api-key:257diff --git a/AGENTS.md b/AGENTS.mdindex 2dfc6fff..07eeb423 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -221,8 +221,9 @@ cargo deny check # dependency policy (i`tests/e2e/handoff_smoke.sh`, `scripts/check-native-packaging.sh`.- CI additionally runs `cargo build --release --bin ai-memory` onLinux/macOS, a Docker image smoke test, `cargo audit` (with the ignores- listed in `ci.yml`), gitleaks secret scanning, and a non-gating Windows- test job.+ listed in `ci.yml`), differential gitleaks scanning, and a non-gating+ Windows test job. `.github/workflows/secret-scan.yml` runs the separate+ weekly/manual full-history gitleaks scan.## Code style guidelinesdiff --git a/SECURITY.md b/SECURITY.mdindex 6449aebf..beb8f3c3 100644--- a/SECURITY.md+++ b/SECURITY.md@@ -101,7 +101,11 @@ what the project is and is not designed to defend against.- **Published executable integrity.** Docker wrapper and standalone hookinstalls use GitHub Release assets with SHA-256 companions. GitHub Actionsare pinned to reviewed commits and release jobs default to read-only token- permissions except the GitHub Release publisher.+ permissions except the GitHub Release publisher. Gitleaks checks each pushed+ or proposed commit range and a separate weekly/manual workflow checks the+ complete reachable history. The full-history scan recognizes only reviewed,+ exact fingerprints in `.gitleaksignore`; adding an entry never substitutes+ for removing the value from the current tree and rotating a real credential.### Out of scope for v1