v0.0.7

Installed over git. This repository does not publish to a registry.

git clone https://github.com/solongate/agent-security
cd agent-security && ./scripts/shell/install.sh

Already installed: solongate update

Checking what you downloaded:

sha256sum -c SHA256SUMS --ignore-missing
gh attestation verify <archive> -R solongate/agent-security
# or offline, from the attached bundle:
gh attestation verify <archive> --bundle <archive>.intoto.jsonl

Changes

• Bump version to 0.0.7 (#59)
• Attach attestation bundles to releases, add fuzz targets for policy parsing
• Bump vulnerable Go module versions, scope release.yml permissions to job level
• Add OpenSSF Scorecard workflow and README badge (#56)
• Match codeql-action SHA pin to the repo's current dependabot bump
• Add OpenSSF Scorecard workflow and README badge
• Bump the actions group with 4 updates (#55)
• Squash merge dev into main (#54)
• Add box-check userns diagnostics: raw bwrap error, plain unshare, capsh, aa-status
• Temporary debug instrumentation: dump generated profile and real path for find -delete investigation
• Fix the two non-required CI failures: box needs the userns sysctl, Seatbelt needs the unlink-through-directory case denied
• Merge dev into main as one commit: Go guard/hook ports, sandbox rework, and the CI workflow fix
• A spinner, where a bar was claiming progress it did not have
• solongate range: how far an update is allowed to move
• It is the TUI, not the dataroom
• A greeting, and three steps that say what to do
• The two guards wrote different records into the same file
• The installer hides the cursor while it holds
• The installer waits instead of asking
• The first run, centred and moving
• The dataroom says what is holding each protected path
• solongate run was human-gated, which broke the thing it is for
• The emblem inside the badge, at 28 pixels
• The official widget, one line under the badges
• One OpenSSF badge, and not in the top row
• The Best Practices emblem, which survives being 14 pixels tall
• Draw the OpenSSF badge with the foundation's own mark
• Say in the README what the OS layer is for
• solongate run: the kernel refuses, not a string matcher
• solongate protect, and an honest account of what holds it
• A first run that waits for a real tool call
• The OpenSSF baseline-1 badge, in the row with the others
• Name the packages after what they are
• Remove solongate-audit, which was never built
• Split the CLI and the TUI into their own modules
• Delete the TypeScript CLI and TUI
• Remove every test in the repository

v0.0.6

Installed over git. This repository does not publish to a registry.

git clone https://github.com/solongate/agent-security
cd agent-security && ./install.sh

Already installed: solongate update

Changes

• Four Go modules named a personal account and the wrong layout
• Fourteen links pointed at a repository that is not there
• OPA 1.21.1 needs go 1.26, and three workflows said 1.25
• ink 5 to 8, react 18 to 19
• Node 20 is end of life, so the floor is 22
• zod 3 to 4
• OPA 1.19.1 to 1.21.1
• Dependabot was opening every npm bump twice
• Bump github.com/mattn/go-isatty
• Two dependencies nothing imports, and the bots kept bumping them
• Bump the dev-tooling group across 1 directory with 6 updates
• Bump the actions group across 1 directory with 4 updates
• The secret scan started charging rent when the repository moved to an org
• docs: clarify Agent Security product identity and repository links
• The repository moved and every link still pointed at where it was
• The gif I fixed was worse than the white corners it fixed
• The rate limit held its ceiling and dropped its floor
• SolonGate is not an MCP gateway, and the repository said it was
• The logo was one I drew, and SolonGate already has one
• Nothing in the repository told anybody how to use it, or join it
• Block degraded to redact on the clients most people use
• The DLP bar named one pattern and meant all of them

v0.0.5

"reason: allowed", and a full-width red bar for a count of seven

Two things on screen that said nothing and looked like they did.

Every allowed call was written down with the reason "allowed". So an entry that
had something real to say printed it and then undid it:

    flagged   DLP: AWS access key
    reason    allowed

The second line restates the decision on the row above and explains nothing. A
reason exists to account for a refusal; where there is nothing to account for the
field is absent now, and the view falls through to the arguments.

The layers panel drew one bar per DLP pattern, each scaled against the busiest —
so the busiest is always full width. With a single pattern that is a full-width
RED bar across the panel for seven hits, which reads as an emergency and carries
no information, because a bar compares and there was nothing to compare against.
Two or more patterns and the comparison is real, so the bars stay; one, and the
number is the whole of what there is to say. The label also had ten columns,
which cut "AWS access key" to "AWS acces…" and named nothing.

0.0.5.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>