Vanta v0.9.7
Vanta v0.9.7
Vanta v0.9.7 closes the relative-path hole left in the v0.9.6 filesystem approval fix and makes Desktop approval scope explicit.
Fixed
- A direct relative
mkdiris resolved from the actual active shell working directory before the kernel assesses it. - The canonical destination appears in the approval action, so the operator can catch wrong-parent paths before execution.
- The approved one-run sandbox binding and the command now use the same
/cd-aware working directory. - Vanta's prompts tell agents to use the exact absolute path for a user-named destination outside the active project instead of assuming
../reaches the intended parent. - Desktop approval checkpoints now offer only Allow once and Reject. Persistent project access modes remain in their dedicated selector.
Brand
- The packaged Desktop icon uses the current Vanta V-in-field mark and violet signal point, matching the public Vanta identity.
Verification
- Focused filesystem, permission, prompt, and Desktop renderer suite: 144 tests passed.
- Core TypeScript and Desktop renderer TypeScript checks passed.
- Full suite: 1,458 test files and 13,616 tests passed, with 3 intentional skips.
- A real default-macOS-Seatbelt dispatch created and verified a GitHub-level sibling directory after one approval; only the empty proof directory was removed afterward.
- The production renderer contains no
Always alloworNever allowcheckpoint action. - The Developer ID-signed macOS package is version 0.9.7, passes strict code-signature verification, and contains the visually inspected 1024 px Vanta brand icon.
- Apple notarization, stapling, Gatekeeper, and public release-asset checks remain the tagged release-workflow boundary.
Full changelog: v0.9.6...v0.9.7