Terms of Service

Version 2026-07-03. These plain-language terms govern use of the MacCrab Rave plugin store. They may be revised as the service evolves; the version in effect is always dated here, and submitters record the version they accepted. This is a plain-language summary, not legal advice.

Technical clarification, 7 September 2026: runtime, capability-display, and submission-status descriptions below have been corrected to match the current product. The acceptance version and liability provisions are unchanged. See product status for current availability and limitations.

These terms cover MacCrab Rave — the plugin catalog served at rave.maccrab.com and consumed by the MacCrab app — and the plugins distributed through it. By browsing the catalog, installing a plugin, or submitting one, you agree to the terms below. If you don’t agree, don’t use the store.

This document sits alongside the Privacy page (what we collect and don’t) and the Verification page (how to verify a plugin yourself). Read those too — the trust model described here is the same one those pages document.

Acceptable use

Use the store for its intended purpose: discovering, verifying, and installing forensic plugins for your own MacCrab installation. Don’t:

• attempt to bypass, forge, or strip the catalog’s signatures or a plugin’s signature;
• submit a plugin you don’t have the right to distribute, or that misrepresents what it does or what it reads;
• use the submission or comment surfaces to distribute malware, spam, or unlawful content;
• probe, scrape, or load the catalog API in a way intended to degrade the service for others;
• impersonate another author or claim a vendor namespace that isn’t yours (see Reserved namespaces).

Plugin authorship and installation at your own risk

A MacCrab plugin is software written by its identified author. First-party plugins are written by MacCrab; community plugins are written by independent authors. A listing records its publisher and version-specific verification information. It is not a warranty that the plugin is fit for your purpose, bug-free, or appropriate for any particular case or jurisdiction.

You install and run plugins at your own risk. You are responsible for deciding whether a given plugin is appropriate for your data and your use, and — where you run it against data belonging to others — for having the authority to do so.

Capability disclosure and install-time consent

Plugin authors must declare the data sources and capabilities their software uses, including file/database access and network or process use. Signed manifests contain capability declarations; catalog pages also present publisher-provided source and output descriptions. These descriptions are intended to inform your decision before installation; neither a schema nor a signature proves that every behavior was declared.

The app asks you to confirm installation. Its current capability descriptions are static by plugin ID rather than derived from each exact version’s manifest. Read the listing’s access and compatibility disclosures as well:

• first-party plugins run unsandboxed after Developer ID and host-team validation, with MacCrab’s privileges including Full Disk Access when granted;
• Posture Pro declares read-only metadata collection and no outbound network use; its first-party execution path does not enforce filesystem or network restrictions;
• community execution and publishing need their own qualification; a catalog badge or declared capability does not establish equivalent containment;
• you can decline at the consent step, and you can remove an installed plugin at any time.

Capability disclosure is a description of what a plugin asks for, not a guarantee about how its author handles what it reads once it runs. Review the disclosure and the plugin’s own documentation before consenting.

First-party vs community channels

The catalog distributes plugins on two channels, and the distinction matters for what these terms cover:

• official (first-party). Plugins built and signed by the MacCrab team, published from the signed catalog mirror. These are our own software.
• contrib (community). Plugins from independent third-party authors, subject to review and signing requirements. These are other people’s software. Their execution path differs from first-party plugins and requires separate qualification.

For community-channel plugins, the author — not MacCrab — is the party responsible for the plugin’s behaviour, its updates, its security response, and its compliance with any license or law. MacCrab operates the catalog and the vetting process; it does not author, control, or stand behind third-party plugins.

The submission page reports the deployed intake setting before login. No community plugins are currently published. An open intake setting does not establish that the complete publishing journey or community runtime has passed qualification. Nothing publishes merely because a submission was accepted.

The signed-supply-chain trust model and revocation

The store verifies a signed supply chain relative to trusted keys:

• the catalog itself is Ed25519-signed by the MacCrab Rave project key;
• each plugin is Ed25519-signed by its publisher key, recorded in the catalog entry;
• community plugins must be reproducible from public source, so anyone can rebuild and confirm the bytes;
• the MacCrab app verifies a signature before loading anything — an unsigned or tampered plugin does not load.

The Verification page explains how to inspect signatures and digests, establish a trusted key, and distinguish those checks from independent source reproducibility and runtime containment.

Revocation. We publish a signed revocations.json. If a plugin or a publisher key is found to be malicious, compromised, or in breach of these terms, we can revoke it; a revoked plugin or key is rejected by MacCrab going forward. Revocation is the primary mechanism for pulling a bad plugin out of the supply chain after the fact — keep your MacCrab able to fetch the current revocation list.

No warranty; limitation of liability

The store and the plugins distributed through it are provided “as is” and “as available,” without warranty of any kind, express or implied, including (without limitation) any implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

For third-party (community-channel) plugins in particular, MacCrab makes no warranty as to their quality, security, accuracy, or fitness, and disclaims liability for any loss or damage arising from your installation or use of them. The vetting gates reduce risk; they do not eliminate it.

To the maximum extent permitted by applicable law, MacCrab and its operator are not liable for any indirect, incidental, special, consequential, or punitive damages, or any loss of data, arising out of your use of the store or any plugin obtained through it.

DMCA / takedown and reserved namespaces

Takedown. If you believe a listed plugin infringes your copyright or other rights, or violates these terms, contact [email protected] with enough detail to identify the plugin and the basis of the complaint. We respond to valid copyright (DMCA-style) notices and to substantiated abuse reports, and may remove or revoke a listing while we review.

Reserved namespaces. The com.maccrab.* plugin-id namespace is reserved for first-party plugins; a community submission claiming it is rejected. A submission whose vendor label is confusingly close to the MacCrab brand is routed to manual owner review rather than auto-merged. See Namespace review in the submission docs.

Operator rights — removal and revocation

MacCrab, as operator of the store, may at its discretion and without prior notice:

• decline, delist, remove, or revoke any plugin — including a first-party one — that is malicious, compromised, broken, mislabeled, infringing, or otherwise in breach of these terms;
• revoke a publisher key via the signed revocation list;
• remove a submission or comment, or restrict an account, for abuse, spam, or breach of acceptable use;
• change the vetting policy, the channel model, or these terms (with the version of the terms in force recorded in the public repo).

These rights are about keeping the supply chain safe; they don’t transfer responsibility for a third-party plugin from its author to MacCrab.

Changes to these terms

We may update these terms; the current version lives in the public repository and the effective version is the one published here. Material changes that affect contributors will be noted before the contrib channel opens.

Contact

Questions, takedown notices, or security concerns: [email protected]. Don’t post security issues in a public comment thread — see the Verification and Privacy pages for the trust and disclosure model.