v7.13.1 — The Co-Author Edition
A security patch: faf-cli's detection no longer follows a link out of your project, so a hostile repo can't pull a file like ~/.aws/credentials into project.faf or your AI's context.
- Detection reads stay inside the project. A README.md, package.json, pyproject.toml or any other repo file that links outside the project, into
.gitor to nothing is treated as absent. Its text never reaches project.faf, CLAUDE.md, AGENTS.md or the output. Links inside the project still work, from the root and from subfolders. faf gitclones withcore.symlinks=false. A cloned repo's links are never followed, and faf never reads a link's path as a file's content.faf cardsreadsagent.fafasafely. Anagent.fafathat links out of its folder is refused in one line, never read or quoted.slotignoredis shown asslotignored, never N/A. A slot is empty,slotignored(from the app-type) or populated.
This predates 7.13. Everyone on faf-cli ^7 should upgrade: npm i -g faf-cli@7.13.1 · bunx faf-cli@7.13.1 · brew upgrade faf-cli.
Tests: 2017 passing, 0 failing. 22 new tests plant a secret behind a symlink and check it never appears. Detection output is byte-identical on link-free repos.
Full notes: CHANGELOG.md
FAF defines. AGENTS.md instructs. AI codes.