[dependabot]

Bumps github.com/plexusone/systemforge from 0.11.0 to 0.30.0.

Release notes

Sourced from github.com/plexusone/systemforge's releases.

v0.30.0

Release Notes: v0.30.0

Full Changelog: plexusone/systemforge@v0.29.0...v0.30.0

v0.29.0

Release Notes: v0.29.0

Full Changelog: plexusone/systemforge@v0.28.0...v0.29.0

v0.28.0

Release Notes: v0.28.0

Full Changelog: plexusone/systemforge@v0.27.0...v0.28.0

v0.27.0

Release Notes: v0.27.0

What's Changed:

• v0.27.0: production hardening and billing on payforge by @​grokify in plexusone/systemforge#71

Full Changelog: plexusone/systemforge@v0.26.0...v0.27.0

v0.26.0

Release Notes: v0.26.0

Full Changelog: plexusone/systemforge@v0.25.0...v0.26.0

v0.25.0

Release Notes: v0.25.0

Full Changelog: plexusone/systemforge@v0.24.0...v0.25.0

v0.24.0

Release Notes: v0.24.0

Full Changelog: plexusone/systemforge@v0.23.0...v0.24.0

v0.23.0

Release Notes: v0.23.0

Full Changelog: plexusone/systemforge@v0.22.0...v0.23.0

v0.22.0

Release Notes: v0.22.0

Full Changelog: plexusone/systemforge@v0.21.0...v0.22.0

v0.21.0

Release Notes: v0.21.0

... (truncated)

Changelog

Sourced from github.com/plexusone/systemforge's changelog.

[v0.30.0] - 2026-10-29

Highlights

• contract/audit/ocsfaudit writes SystemForge's security events as OCSF 1.10 events, one JSON object per line, to an io.Writer the host names, for a security data lake or SIEM that ingests OCSF
• audit.NewMultiEmitter hands every security event to several emitters, such as the log emitter and the OCSF emitter

Security

• OCSF events identify people only by principal ID and client address: names, email addresses, session tokens, tokens, token and code prefixes, codes and free-text reasons are left out of every field (a revoked managed-principal session is named by its record UUID), and event details reach the output only through a per-event-type allowlist of codes, UUIDs, booleans, integers and times (f8f5d44)
• The client sends the User-Agent, so it can carry an email address or a token; both the log emitter and the OCSF emitter now record it only through audit.SanitizeUserAgent, which removes control characters and then leaves out a value that looks like it holds an email address or a credential (a heuristic for the common shapes) (8eaa650)
• Token and authorization code replay events are High severity with is_alert, a platform-admin grant is High, and a production waiver at startup is Medium (f8f5d44)

Added

• ocsfaudit.New(w, Options): an audit.Emitter that maps each event to an OCSF class (Authentication, User Management, Group Management, Entity Management, Application Lifecycle, or Base Event for an unknown type), entities OCSF has no type for as type_id Other with the type named,, with product, vendor and deployment metadata (metadata.reporter.name), the organization in metadata.tenant_uid and the request ID in metadata.correlation_uid (f8f5d44)
• Emit never blocks, logs or fails the request: it queues each line in a bounded buffer written by one goroutine, and drops and counts events when the buffer is full (Dropped) or cannot encode them (EncodeFailures); a reporter goroutine logs the counts once a minute and on Close, write failures and short writes are counted (WriteFailures) and logged at most once a minute, a line torn by a failed write is the only one lost, and Close drains, flushes and syncs (423324d)
• audit.MultiEmitter and audit.NewMultiEmitter (76693ba)
• Dependency github.com/grokify/ocsf-schema-go v0.2.0 (d9c1761)
• audit.SanitizeUserAgent: removes control characters and invalid UTF-8, then leaves out a User-Agent that looks like it holds an email address or a credential, and cuts any other to 512 bytes (8eaa650)

Changed

• audit.LogEmitter leaves out a User-Agent that holds an email address or a credential-like value (8eaa650)

Documentation

• docs/security/ocsf-events.md: wiring with an append-mode file, the event mapping, fields, privacy rules and buffering (66895d1)
• The README and the documentation home feature security events and OCSF output (bbece5f)
• The OCSF page states the schema version 1.10.0-dev, recommends rotating by renaming over copytruncate, and describes delivery, session IDs and the User-Agent exactly (cabf495)
• The README's privacy claim covers the OCSF emitter and says what the log emitter records; rotation by renaming waits for the reopen and uses delaycompress with compression (23c5e87)

Tests

• The OCSF output of every security event type, with success and failure variants, validates against the schema embedded in ocsf-schema-go (7b8d38e)
• The tests proving no token or secret reaches a log or event also run the OCSF emitter, and email verification and change events carry no address (b0e01a3)
• Every event, Base Event included, validates through ValidateEvent with no skipped issues; torn lines, short writes, Emit with a stuck logger, periodic drop reports, unsyncable files and User-Agent sanitizing are tested (423324d)
• A torn line stays marked through a failed Write that wrote nothing, and control characters cannot hide an email address from the User-Agent check (0300d41)

[v0.29.0] - 2026-10-29

Highlights

• SystemAuth asks for consent by the client's party: clients get party (first_party, second_party or third_party) and an optional logo_url, only first-party clients skip the consent screen, and social_login.skip_consent no longer auto-consents every client
• The authorization endpoint honours the OIDC prompt parameter, so a first-party application can sign a user in silently, and the login chooser names the requesting client and shows its logo
• Verified email: with a new mail section, SystemAuth verifies an unverified provider email at sign-in, lets a signed-in person change their email at /account/email, and carries email_verified_at in ID tokens and UserInfo
• Configuration secrets resolve through an omnivault vault named in secrets.vault, with the environment as the default, and no cloud SDK in the library packages
• systemauth org member add|remove|list, organization slug resolution for relying parties, and read-only application vocabularies in the product contract API

Breaking

... (truncated)

Commits

• 0cf6830 Merge pull request #76 from plexusone/feat/ocsf-audit
• 630964b docs(release): add the second review round to the v0.30.0 changelog
• 23c5e87 docs(audit): narrow the privacy claims and qualify rotation
• 0300d41 fix(audit): keep a torn line marked and clean User-Agent before checking it
• 4cbc7e3 docs(release): update the v0.30.0 changelog for the review fixes
• cabf495 docs(audit): correct the OCSF delivery, privacy and version notes
• 8eaa650 fix(audit): keep personal data in User-Agent out of security events
• 423324d fix(audit): keep OCSF lines whole and logging off the request path
• d9c1761 build(deps): update ocsf-schema-go to v0.2.0
• 0ed8cf1 docs(release): list the README update in the v0.30.0 changelog
• Additional commits viewable in compare view

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: d9c50628-547c-4e69-9230-ecd6beae0982

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn