Skip to main content

Anthropic/compliance

@webframp/anthropic/compliancev2026.11.03.1· Apache-2.0· 17d agoBEHAVIORSREPORTS
01README

Observe a Claude Enterprise account via the Compliance API. Covers the 6-year activity audit feed, organization directory (users, roles, groups with SCIM source attribution), and effective runtime settings (retention, redaction, IP allowlist, SSO mode, code execution egress).

Authentication

Requires a Compliance Access Key created by the primary owner in claude.ai → Org settings → API access. Store in a swamp vault.

Usage

swamp extension pull @webframp/anthropic/compliance
swamp vault create local_encryption anthropic   # once, if you have no vault yet
swamp vault put anthropic COMPLIANCE_KEY        # prompts; never pass the value
swamp model create @webframp/anthropic/compliance claude-compliance \
  --global-arg 'complianceKey=${{ vault.get("anthropic", "COMPLIANCE_KEY") }}'

# Discover org
swamp model method run claude-compliance sync_organizations

# Full directory sync (users + roles + groups)
swamp model method run claude-compliance sync_directory

# Effective settings
swamp model method run claude-compliance sync_effective_settings

# Audit feed
swamp model method run claude-compliance collect_activities
swamp model method run claude-compliance collect_activities \
  --input activity_types=claude_chat_created,github_integration_updated
# One user's history, walking back through older pages
swamp model method run claude-compliance collect_activities \
  --input actor_ids=user_01abc --input limit=1000 --input max_pages=10

Methods

  • sync_organizations — discover orgs visible to the key
  • sync_users — paginate all directory users
  • sync_roles — list defined roles
  • sync_groups — list groups
  • get_group_members — members with SCIM source attribution
  • sync_directory — fan-out: users + roles + groups in one call
  • sync_effective_settings — observe runtime config
  • collect_activities — audit feed (6-year retention); filter by type, actor, time window; page back with max_pages / after_id

Reports

  • config-snapshot — aggregates effective settings, roles, groups, organizations, and directory user count (never the roster itself) into one JSON artifact, for exporting to a git-tracked config repo. Runs as a default report on every method call.
02Release Notes

2026.11.03.1

Changed: Bump zod 4.6.5 → 4.6.7

2026.10.21.1

Changed: Documentation only: the README, the registry description, and the complianceKey global argument description no longer print a token-shaped key prefix. The argument description now says to supply the key as ${{ vault.get("anthropic", "COMPLIANCE_KEY") }}. The README and the registry Quick Start now create the vault if needed and store the key with the interactive swamp vault put anthropic COMPLIANCE_KEY prompt before creating the model.

Upgrade note: No code, schema, or behavioral changes. The model version moves to 2026.10.21.1 with an identity upgrade.

03Behaviors1
@webframp/anthropic/compliancev2026.11.03.1anthropic/compliance.ts

Global Arguments

ArgumentTypeDescription
complianceKeystringCompliance Access Key from claude.ai org settings. Supply it as ${{ vault.get("anthropic", "COMPLIANCE_KEY") }}; never pass the literal key
orgId?stringOrganization ID to scope queries. Omit to auto-discover from /v1/compliance/organizations.
fn collect_activities(activity_types?: string, actor_ids?: string, since?: string, until?: string, limit?: string, after_id?: string, max_pages?: string)
Collect compliance activities, newest first. Filter by activity_types, actor_ids (directory user IDs) and a created_at window (since/until). Follow older pages with max_pages or resume from a previous next_cursor via after_id.
ArgumentTypeDescription
activity_types?stringComma-separated activity type filter (e.g. 'claude_chat_created,github_integration_updated')
actor_ids?stringComma-separated user IDs to filter by actor (e.g. 'user_01abc,user_01def'); IDs come from sync_users
since?stringISO-8601 timestamp — collect activities created at or after this time
until?stringISO-8601 timestamp — collect activities created at or before this time
limit?stringMax activities to collect per page (default 100, max 5000)
after_id?stringCursor from a previous run's next_cursor; resumes at the next older page
max_pages?stringMax pages to fetch while has_more is true (default 1, max 50)
fn sync_organizations()
Discover organizations visible to the compliance key.
fn sync_users()
Sync all directory users for the organization. Paginates automatically.
fn sync_roles()
Sync roles defined for the organization.
fn sync_groups()
Sync groups for the organization. Use get_group_members for member detail with SCIM source attribution.
fn get_group_members(groupId: string)
Get members of a specific group, including SCIM source attribution (direct vs scim).
ArgumentTypeDescription
groupIdstringGroup ID to fetch members for
fn sync_effective_settings()
Observe effective runtime settings: data retention, content redaction, IP allowlist, SSO mode, code execution egress.
fn sync_directory()
Fan-out: sync users, roles, and groups for the organization in one method call.

Resources

activities(1h)— Compliance activity feed (audit trail, 6-year retention)
organizations(24h)— Organizations visible to the compliance key
users(1h)— Directory users for an organization
roles(24h)— Roles defined for an organization
groups(24h)— Groups defined for an organization
groupMembers(1h)— Members of a specific group with SCIM source attribution
effectiveSettings(1h)— Effective runtime settings (retention, redaction, IP allowlist, SSO mode)
04Reports1
@webframp/compliance-config-snapshotmethod
config_snapshot_report.ts

Aggregate effective settings, roles, groups, organizations, and directory user count into one git-diffable config snapshot

anthropiccomplianceconfigsnapshot
05Previous Versions19
2026.10.21.1Apache-2.0

2026.10.21.1

Changed: Documentation only: the README, the registry description, and the complianceKey global argument description no longer print a token-shaped key prefix. The argument description now says to supply the key as ${{ vault.get("anthropic", "COMPLIANCE_KEY") }}. The README and the registry Quick Start now create the vault if needed and store the key with the interactive swamp vault put anthropic COMPLIANCE_KEY prompt before creating the model.

Upgrade note: No code, schema, or behavioral changes. The model version moves to 2026.10.21.1 with an identity upgrade.

2026.10.14.1Apache-2.0(was none)

2026.10.14.1

Added: The manifest now declares license: Apache-2.0 (SPDX). The registry quality rubric scores a declared license separately from the bundled LICENSE.md.

Upgrade note: Metadata only. No code, schema, or behavioral changes.

2026.10.07.1

Bug fix: sync_users, sync_directory and get_group_members failed with HTTP 400 (Unknown query parameter: 'after_id'). The directory endpoints page with an opaque next_page token passed back as page; the extension sent the activity feed's after_id cursor. Pagination now follows next_page, and sync_roles, sync_groups and sync_directory follow it too instead of reading only the first page.

User records now read full_name and organization_role (the fields the API returns) into the existing name and role attributes, which were previously always empty. Group members use user_id as id.

Feature: collect_activities can now target one user's history and walk back through the feed:

  • actor_ids filters by directory user ID (comma-separated; IDs come from sync_users).
  • until bounds the window above, alongside the existing since.
  • max_pages follows has_more through older pages (default 1, max 50).
  • after_id resumes from the next_cursor a previous run stored.

The activity resource gains optional next_cursor, pages and filters fields (a cursor is only valid for the same filters), and the actor schema now includes user_id and email_address, the keys the API uses on user_actor records. No breaking schema changes.

Behavior changes in collect_activities:

  • since and until must be ISO-8601 and are normalized to UTC (2026-10-01T02:00:00+02:00 is sent as 2026-10-01T00:00:00.000Z). A date-only value means 00:00Z that day. A value with a time must carry Z or an offset, since otherwise the window would depend on the host's timezone. Impossible dates such as 2026-02-31, years outside 1970–9998, and an until earlier than since are rejected.
  • limit and max_pages must be positive integers. A non-numeric or non-positive value now fails with a clear error instead of being forwarded or silently replaced by the default.
  • A cursor that does not advance ends the walk instead of repeating requests. The output then keeps has_more: true, sets stalled: true and leaves next_cursor null, so a truncated feed is never reported as complete.

Truncation reporting: directory reads report has_more: true whenever data may remain unread: the 20-page cap was reached, the API claimed more data without a usable next_page, or the token repeated. get_group_members now pages the group list when resolving the group name, records has_more, and URL-encodes the group ID. sync_directory now fetches users, roles and groups before writing any of them, so a failure partway through leaves no partial update. The config-snapshot report marks the directory user count truncated, and adds rolesTruncated / groupsTruncated flags, when a list was cut short.

2026.10.06.1

Bug fix: collect_activities now honors the activity_types filter. It previously sent a bare activity_types query parameter, which the Compliance API rejects with HTTP 400; it now sends repeated activity_types[] values. The comma-separated argument is split and trimmed, and empty entries are dropped. Example names in the docs now use real activity types such as claude_chat_created and github_integration_updated.

2026.09.18.1

Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the repo. No behavioral changes in this extension.

2026.10.07.1

2026.10.07.1

Bug fix: sync_users, sync_directory and get_group_members failed with HTTP 400 (Unknown query parameter: 'after_id'). The directory endpoints page with an opaque next_page token passed back as page; the extension sent the activity feed's after_id cursor. Pagination now follows next_page, and sync_roles, sync_groups and sync_directory follow it too instead of reading only the first page.

User records now read full_name and organization_role (the fields the API returns) into the existing name and role attributes, which were previously always empty. Group members use user_id as id.

Feature: collect_activities can now target one user's history and walk back through the feed:

  • actor_ids filters by directory user ID (comma-separated; IDs come from sync_users).
  • until bounds the window above, alongside the existing since.
  • max_pages follows has_more through older pages (default 1, max 50).
  • after_id resumes from the next_cursor a previous run stored.

The activity resource gains optional next_cursor, pages and filters fields (a cursor is only valid for the same filters), and the actor schema now includes user_id and email_address, the keys the API uses on user_actor records. No breaking schema changes.

Behavior changes in collect_activities:

  • since and until must be ISO-8601 and are normalized to UTC (2026-10-01T02:00:00+02:00 is sent as 2026-10-01T00:00:00.000Z). A date-only value means 00:00Z that day. A value with a time must carry Z or an offset, since otherwise the window would depend on the host's timezone. Impossible dates such as 2026-02-31, years outside 1970–9998, and an until earlier than since are rejected.
  • limit and max_pages must be positive integers. A non-numeric or non-positive value now fails with a clear error instead of being forwarded or silently replaced by the default.
  • A cursor that does not advance ends the walk instead of repeating requests. The output then keeps has_more: true, sets stalled: true and leaves next_cursor null, so a truncated feed is never reported as complete.

Truncation reporting: directory reads report has_more: true whenever data may remain unread: the 20-page cap was reached, the API claimed more data without a usable next_page, or the token repeated. get_group_members now pages the group list when resolving the group name, records has_more, and URL-encodes the group ID. sync_directory now fetches users, roles and groups before writing any of them, so a failure partway through leaves no partial update. The config-snapshot report marks the directory user count truncated, and adds rolesTruncated / groupsTruncated flags, when a list was cut short.

2026.10.06.1

Bug fix: collect_activities now honors the activity_types filter. It previously sent a bare activity_types query parameter, which the Compliance API rejects with HTTP 400; it now sends repeated activity_types[] values. The comma-separated argument is split and trimmed, and empty entries are dropped. Example names in the docs now use real activity types such as claude_chat_created and github_integration_updated.

2026.09.18.1

Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the repo. No behavioral changes in this extension.

2026.10.06.1

2026.10.06.1

Bug fix: collect_activities now honors the activity_types filter. It previously sent a bare activity_types query parameter, which the Compliance API rejects with HTTP 400; it now sends repeated activity_types[] values. The comma-separated argument is split and trimmed, and empty entries are dropped. Example names in the docs now use real activity types such as claude_chat_created and github_integration_updated.

2026.09.18.1

Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the repo. No behavioral changes in this extension.

2026.09.18.1

2026.09.18.1

Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the repo. No behavioral changes in this extension.

2026.09.15.1

2026.09.15.1

Changed: Bump zod 4.4.3 → 4.6.5

2026.08.28.1

Changed: Normalized the extension license to Apache-2.0 and corrected the copyright holder to "Sean Escriva". Extensions that previously shipped an MIT LICENSE.md are now Apache-2.0, consistent with the repository root and every other extension. No code or behavioral changes.

Upgrade note: License text only. No API, schema, or runtime behavior changed.

2026.08.26.3

Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry quality scorer can resolve dependencies and score the extension. An earlier release used a bare "zod" import-map specifier, which published but scored as unscored.

Changed: Retained explicit compilerOptions.strict in deno.json. No behavioral or schema changes.

2026.08.28.1

2026.08.28.1

Changed: Normalized the extension license to Apache-2.0 and corrected the copyright holder to "Sean Escriva". Extensions that previously shipped an MIT LICENSE.md are now Apache-2.0, consistent with the repository root and every other extension. No code or behavioral changes.

Upgrade note: License text only. No API, schema, or runtime behavior changed.

2026.08.26.3

Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry quality scorer can resolve dependencies and score the extension. An earlier release used a bare "zod" import-map specifier, which published but scored as unscored.

Changed: Retained explicit compilerOptions.strict in deno.json. No behavioral or schema changes.

2026.08.26.3

2026.08.26.3

Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry quality scorer can resolve dependencies and score the extension. An earlier release used a bare "zod" import-map specifier, which published but scored as unscored.

Changed: Retained explicit compilerOptions.strict in deno.json. No behavioral or schema changes.

2026.08.26.1

2026.08.26.1

Fixed: Added missing description field to upgrade entry for version 2026.08.24.2. The omission caused swamp extension pull to fail with a catalog validation error ("upgrades.N.description: Invalid input: expected string, received undefined").

2026.08.25.1

2026.08.25.1

Changed: Updated labels for improved extension discoverability. Added cross-cutting category labels (security, observability, finops, infrastructure, networking, compliance, devops, ai, incident-response) where applicable.

updated labels

2026.08.24.3

2026.08.24.3

Added: Output metadata attributes for observability.

  • durationMs: Method execution duration in milliseconds.
  • collectedBy: Extension name that produced the data.
  • fetchedAt: ISO 8601 timestamp when data was fetched (added to resources that previously lacked it).
2026.08.24.2

2026.08.24.2

Fixed source/manifest version mismatch. Added Troubleshooting section documenting the 600 req/min shared rate limit with no backoff, paginateAll 20K cap, single-page activities, best-effort group name resolution, orgId auto-discovery, and no-retry behavior.

2026.08.21.2

2026.08.21.2

Changed: collect_activities's since argument is now validated as a parseable timestamp before being sent to the API — previously a malformed value passed straight through and only surfaced as an opaque upstream 400.

get_group_members's best-effort group-name lookup no longer swallows its failure silently; a failed lookup now logs a message naming the group ID and the underlying error before falling back to using the ID as the display name.

The config-snapshot report's data reads no longer treat a storage-backend failure and "this spec was never collected" identically. A failed getContent call or unparseable JSON now logs a warning naming the spec and model instance before the report falls back to omitting that section.

2026.08.21.1

2026.08.21.1

Changed: Added descriptions to every previously undocumented field across the activities, organizations, users, roles, groups, groupMembers, and effectiveSettings resource schemas. No behavioral change.

2026.07.30.1

Fixed: sync_groups and sync_directory returned HTTP 404 from the Anthropic Compliance API. The org-scoped groups endpoint (/v1/compliance/organizations/{orgId}/groups) no longer exists; groups are now served at the top-level path /v1/compliance/groups.

Changed: All three call sites that listed groups (sync_groups, sync_directory, and the name-lookup fallback in get_group_members) now use /v1/compliance/groups instead of the former org-scoped path.

Upgrade note: No action required. The resource schema and instance names are unchanged — only the upstream API path differs. Re-run sync_groups or sync_directory after upgrading to populate the groups resource.

2026.07.30.1

2026.07.30.1

Fixed: sync_groups and sync_directory returned HTTP 404 from the Anthropic Compliance API. The org-scoped groups endpoint (/v1/compliance/organizations/{orgId}/groups) no longer exists; groups are now served at the top-level path /v1/compliance/groups.

Changed: All three call sites that listed groups (sync_groups, sync_directory, and the name-lookup fallback in get_group_members) now use /v1/compliance/groups instead of the former org-scoped path.

Upgrade note: No action required. The resource schema and instance names are unchanged — only the upstream API path differs. Re-run sync_groups or sync_directory after upgrading to populate the groups resource.

2026.07.18.1

2026.07.17.1

Added:

  • New config-snapshot report (@webframp/compliance-config-snapshot), registered as a default report on the model type. Aggregates the latest effectiveSettings, roles, groups, and organizations, plus the directory user count (never the roster), into one JSON artifact — swamp report get @webframp/compliance-config-snapshot --model claude-compliance --json. Intended to be exported into a git-tracked config repo so drift and growth are visible via git log/git diff. Individual users and group membership are deliberately excluded: that data is SCIM/Entra-owned, not config, and carries PII.

2026.07.15.1

Fixed:

  • sync_users, sync_roles, sync_groups, sync_effective_settings, and the sync_directory fan-out all wrote their resource using the organization ID as the instance name. Since every one of those specs shared the same instance name, each sync method's write landed as a new version of the same data artifact rather than its own resource — running sync_roles after sync_effective_settings silently pushed the effective settings snapshot into history, and swamp data get claude-compliance <orgId> would return whichever spec synced most recently, not a specific one.

Changed:

  • These methods now write to a fixed instance name equal to their own spec name ("users", "roles", "groups", "effectiveSettings") instead of the organization ID, matching the existing pattern used by collect_activities ("recent") and sync_organizations ("all") — each spec's instance name is exclusive to that spec, since swamp's storage key is (modelId, name) and does not include specName. An earlier draft of this fix used a single shared literal ("current") for all four specs, which reproduced the exact same collision under a different name; that was caught in review before release.
  • get_group_members now writes to member:<groupId> instead of the bare groupId. Since groupId is caller-supplied, an unnamespaced write could collide with one of the new fixed literals above (e.g. a group ID of "users" would have landed on the same data name as sync_users).

Upgrade note: Data written under the old org-ID-keyed name by previous versions is orphaned by this change — it remains in history (subject to each resource's normal GC policy) but is no longer returned by swamp data get claude-compliance <orgId>. Re-run sync_users, sync_roles, sync_groups, and sync_effective_settings (or sync_directory) after upgrading, then read them back with swamp data get claude-compliance users / roles / groups / effectiveSettings. Group member data moves from swamp data get claude-compliance <groupId> to swamp data get claude-compliance member:<groupId> — update any CEL expressions or scripts referencing the old form.

2026.07.07.1

Fixed:

  • collect_activities since filter: the Compliance API expects the dotted range parameter created_at.gte, not the bracketed created_at[gte], which returned HTTP 400 (Unknown query parameter: 'created_at[gte]'). The since argument now filters activities correctly.

2026.07.03.1

Fixed:

  • Organization ID mapping: The Anthropic compliance API returns org identifiers in the uuid field, not id. resolveOrgId and sync_organizations now correctly prefer uuid over id, fixing auto-discovery failures.
  • Activity schema: actor.id, actor.email, actor.name, and details are now nullable+optional, matching actual API response shapes (e.g. api_actor has api_key_id but no id/email/name).

Changed:

  • collect_activities now writes to the "recent" instance (was "latest"). swamp reserves "latest" for internal use. If you have CEL expressions referencing data.latest("claude-compliance", "latest"), update them to data.latest("claude-compliance", "recent").

2026.07.02.1

Added: Initial release. Compliance API observation model with 8 methods: sync_organizations, sync_users, sync_roles, sync_groups, get_group_members, sync_directory (fan-out), sync_effective_settings, collect_activities. Seven versioned resource specs for CEL queries.

2026.07.17.1

2026.07.17.1

Added:

  • New config-snapshot report (@webframp/compliance-config-snapshot), registered as a default report on the model type. Aggregates the latest effectiveSettings, roles, groups, and organizations, plus the directory user count (never the roster), into one JSON artifact — swamp report get @webframp/compliance-config-snapshot --model claude-compliance --json. Intended to be exported into a git-tracked config repo so drift and growth are visible via git log/git diff. Individual users and group membership are deliberately excluded: that data is SCIM/Entra-owned, not config, and carries PII.

2026.07.15.1

Fixed:

  • sync_users, sync_roles, sync_groups, sync_effective_settings, and the sync_directory fan-out all wrote their resource using the organization ID as the instance name. Since every one of those specs shared the same instance name, each sync method's write landed as a new version of the same data artifact rather than its own resource — running sync_roles after sync_effective_settings silently pushed the effective settings snapshot into history, and swamp data get claude-compliance <orgId> would return whichever spec synced most recently, not a specific one.

Changed:

  • These methods now write to a fixed instance name equal to their own spec name ("users", "roles", "groups", "effectiveSettings") instead of the organization ID, matching the existing pattern used by collect_activities ("recent") and sync_organizations ("all") — each spec's instance name is exclusive to that spec, since swamp's storage key is (modelId, name) and does not include specName. An earlier draft of this fix used a single shared literal ("current") for all four specs, which reproduced the exact same collision under a different name; that was caught in review before release.
  • get_group_members now writes to member:<groupId> instead of the bare groupId. Since groupId is caller-supplied, an unnamespaced write could collide with one of the new fixed literals above (e.g. a group ID of "users" would have landed on the same data name as sync_users).

Upgrade note: Data written under the old org-ID-keyed name by previous versions is orphaned by this change — it remains in history (subject to each resource's normal GC policy) but is no longer returned by swamp data get claude-compliance <orgId>. Re-run sync_users, sync_roles, sync_groups, and sync_effective_settings (or sync_directory) after upgrading, then read them back with swamp data get claude-compliance users / roles / groups / effectiveSettings. Group member data moves from swamp data get claude-compliance <groupId> to swamp data get claude-compliance member:<groupId> — update any CEL expressions or scripts referencing the old form.

2026.07.07.1

Fixed:

  • collect_activities since filter: the Compliance API expects the dotted range parameter created_at.gte, not the bracketed created_at[gte], which returned HTTP 400 (Unknown query parameter: 'created_at[gte]'). The since argument now filters activities correctly.

2026.07.03.1

Fixed:

  • Organization ID mapping: The Anthropic compliance API returns org identifiers in the uuid field, not id. resolveOrgId and sync_organizations now correctly prefer uuid over id, fixing auto-discovery failures.
  • Activity schema: actor.id, actor.email, actor.name, and details are now nullable+optional, matching actual API response shapes (e.g. api_actor has api_key_id but no id/email/name).

Changed:

  • collect_activities now writes to the "recent" instance (was "latest"). swamp reserves "latest" for internal use. If you have CEL expressions referencing data.latest("claude-compliance", "latest"), update them to data.latest("claude-compliance", "recent").

2026.07.02.1

Added: Initial release. Compliance API observation model with 8 methods: sync_organizations, sync_users, sync_roles, sync_groups, get_group_members, sync_directory (fan-out), sync_effective_settings, collect_activities. Seven versioned resource specs for CEL queries.

Added 1 reports

2026.07.15.1

2026.07.15.1

Fixed:

  • sync_users, sync_roles, sync_groups, sync_effective_settings, and the sync_directory fan-out all wrote their resource using the organization ID as the instance name. Since every one of those specs shared the same instance name, each sync method's write landed as a new version of the same data artifact rather than its own resource — running sync_roles after sync_effective_settings silently pushed the effective settings snapshot into history, and swamp data get claude-compliance <orgId> would return whichever spec synced most recently, not a specific one.

Changed:

  • These methods now write to a fixed instance name equal to their own spec name ("users", "roles", "groups", "effectiveSettings") instead of the organization ID, matching the existing pattern used by collect_activities ("recent") and sync_organizations ("all") — each spec's instance name is exclusive to that spec, since swamp's storage key is (modelId, name) and does not include specName. An earlier draft of this fix used a single shared literal ("current") for all four specs, which reproduced the exact same collision under a different name; that was caught in review before release.
  • get_group_members now writes to member:<groupId> instead of the bare groupId. Since groupId is caller-supplied, an unnamespaced write could collide with one of the new fixed literals above (e.g. a group ID of "users" would have landed on the same data name as sync_users).

Upgrade note: Data written under the old org-ID-keyed name by previous versions is orphaned by this change — it remains in history (subject to each resource's normal GC policy) but is no longer returned by swamp data get claude-compliance <orgId>. Re-run sync_users, sync_roles, sync_groups, and sync_effective_settings (or sync_directory) after upgrading, then read them back with swamp data get claude-compliance users / roles / groups / effectiveSettings. Group member data moves from swamp data get claude-compliance <groupId> to swamp data get claude-compliance member:<groupId> — update any CEL expressions or scripts referencing the old form.

2026.07.07.1

Fixed:

  • collect_activities since filter: the Compliance API expects the dotted range parameter created_at.gte, not the bracketed created_at[gte], which returned HTTP 400 (Unknown query parameter: 'created_at[gte]'). The since argument now filters activities correctly.

2026.07.03.1

Fixed:

  • Organization ID mapping: The Anthropic compliance API returns org identifiers in the uuid field, not id. resolveOrgId and sync_organizations now correctly prefer uuid over id, fixing auto-discovery failures.
  • Activity schema: actor.id, actor.email, actor.name, and details are now nullable+optional, matching actual API response shapes (e.g. api_actor has api_key_id but no id/email/name).

Changed:

  • collect_activities now writes to the "recent" instance (was "latest"). swamp reserves "latest" for internal use. If you have CEL expressions referencing data.latest("claude-compliance", "latest"), update them to data.latest("claude-compliance", "recent").

2026.07.02.1

Added: Initial release. Compliance API observation model with 8 methods: sync_organizations, sync_users, sync_roles, sync_groups, get_group_members, sync_directory (fan-out), sync_effective_settings, collect_activities. Seven versioned resource specs for CEL queries.

2026.07.07.1

2026.07.07.1

Fixed:

  • collect_activities since filter: the Compliance API expects the dotted range parameter created_at.gte, not the bracketed created_at[gte], which returned HTTP 400 (Unknown query parameter: 'created_at[gte]'). The since argument now filters activities correctly.

2026.07.03.1

Fixed:

  • Organization ID mapping: The Anthropic compliance API returns org identifiers in the uuid field, not id. resolveOrgId and sync_organizations now correctly prefer uuid over id, fixing auto-discovery failures.
  • Activity schema: actor.id, actor.email, actor.name, and details are now nullable+optional, matching actual API response shapes (e.g. api_actor has api_key_id but no id/email/name).

Changed:

  • collect_activities now writes to the "recent" instance (was "latest"). swamp reserves "latest" for internal use. If you have CEL expressions referencing data.latest("claude-compliance", "latest"), update them to data.latest("claude-compliance", "recent").

2026.07.02.1

Added: Initial release. Compliance API observation model with 8 methods: sync_organizations, sync_users, sync_roles, sync_groups, get_group_members, sync_directory (fan-out), sync_effective_settings, collect_activities. Seven versioned resource specs for CEL queries.

06Stats
A
100 / 100
Downloads
45
Archive size
23.8 KB
  • Has README or module doc2/2earned
  • README has a code example1/1earned
  • README is substantive1/1earned
  • Most symbols documented1/1earned
  • No slow types (deprecated)1/1earned
  • Dependencies pass trust audit2/2earned
  • Docs keep secrets in a vault1/1earned
  • Has description1/1earned
  • Platform support declared (or universal)2/2earned
  • License2/2earned
  • Verified public repository2/2earned
07Platforms
08Labels