Tags

Tags give the ability to mark specific points in history as being important

  • v0.5.0

    115bd53b · feat: add isolated Lighthouse audits · 
    Rankrat v0.5.0

Add five boundary-limited Lighthouse operations across every transport with an
isolated Chromium worker, hardened deployment, and complete release coverage.

  • v0.4.1

    f8cdd994 · fix: remediate cryptography advisory · 
    Rankrat v0.4.1

Upgrade uv to 0.11.31 and cryptography to 50.0.0, remove the resolved advisory
exceptions, and harden the cold-start production MCP smoke timeout.

  • v0.4.0

    ed57bb55 · fix: harden provider and release boundaries · 
    Rankrat v0.4.0

Add GA4 account, property, and data-stream inventory and rename operations;
clarify GA4 placement diagnostics; provide native OpenClaw MCP integration;
and harden provider errors, local credentials, live verification, image smoke
tests, and vulnerability exception evidence.

  • v0.3.0

    f6083eef · feat!: drop the GA4 parent-account pin from the boundary file · 
    v0.3.0 — drop the GA4 parent-account pin

The boundary file no longer carries google_analytics_parent_account_id. It only
ever decided which GA4 account a newly created property was filed under, never
narrowed a read, and silently fixed that choice forever. The caller now supplies
the parent per onboarding request.

Breaking: delete the field from every account in boundaries.json, or startup
fails on the unknown key.

  • v0.2.0

    93c1dc85 · feat: serve the onboarding procedure and gate the agent path · 
    v0.2.0 — serve the onboarding procedure, gate the agent path

Rankrat cannot verify site ownership, so onboarding reports success while the
properties are unverified and returning nothing. The steps only an operator can
perform are now served as the rankrat://onboarding resource, a per-site template
and an onboarding_guide tool, narrowed by whether the property is a Domain or a
URL-prefix form.

Breaking: site_onboarding_submit now needs RANKRAT_ALLOW_AGENT_ONBOARDING=true
as well as writable mode, because it is the only operation that rewrites the
boundary file the server enforces.

  • v0.1.2

    8af031a6 · feat: add the rankrat.sh wrapper and fix the boundary mount · 
    v0.1.2 — rankrat.sh, and a boundary mount that works

Mounting the boundary file on its own never worked: the image bakes /run/config
owned by its own user, so a single-file bind mount leaves that directory
untraversable to a container running as the host user. Every Make target that
started the production image did exactly that. Everything now mounts the
directory.

rankrat.sh wraps docker run for the published image and the Makefile delegates
to it, so the invocation exists once. The README leads with the image, and
server.json now uses the canonical OCI reference the MCP registry requires.

  • v0.1.1

    1847a08b · fix: publish to the MCP registry and document the PageSpeed key · 
    v0.1.1 — MCP registry publish + PageSpeed key docs

server.json's description exceeded the registry's 100-character cap, which is
reported as a 422 from the publish call after every other artifact has shipped,
so v0.1.0 reached Docker Hub, GitHub Releases and ClawHub but not the registry.

Also documents obtaining and restricting the PageSpeed API key, that it takes a
container path rather than a host path, and that PageSpeed alone among the
Google surfaces does not use OAuth.

  • v0.1.0

    995d3bcd · feat: one read-only switch, trusted onboarding, and an agent surface · 
    v0.1.0 — initial release

RANKRAT_READ_ONLY replaces the per-write approval and admin-token design.
Default true, and write tools are absent from tools/list rather than refused, so
an agent cannot discover them.

RANKRAT_UNBOUNDED adds reusable trusted-onboarding sessions that keep credential
accounts fixed while relaxing per-resource allow-lists, then persist the exact
onboarded resource IDs back to the boundary file.

Breaking: RANKRAT_ENABLE_WRITES and RANKRAT_ADMIN_BEARER_SECRET_FILE are gone,
and unknown RANKRAT_* names now fail startup.

Ships .agents/ with a skill, both plugin manifests and a dual-transport MCP
bridge; gates the image build behind lint and tests; relicenses to WTFPL with a
third-party notice.