Skip to content

v0.0.7

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 14 Oct 14:00
· 417 commits to main since this release
v0.0.7
7d8ae60
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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
Assets 15
Loading