# Granite Guardian > Granite Guardian is IBM's family of open-weight judge models. The current 8-billion-parameter release answers yes or no on whether a prompt, response, retrieved context or function call meets a built-in or custom criterion, and the owner runs it. - Canonical: https://www.anchorterminal.com/tools/granite-guardian - Markdown: https://www.anchorterminal.com/tools/granite-guardian.md (~7,150 tokens) - Slim: https://www.anchorterminal.com/tools/granite-guardian.min.md (~1,680 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/granite-guardian.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-09 ## Overview **Grade C · 60.1/100 · rank #478 of 842 · #10 in Guardrails & safety filters · not agent-ready · confidence medium** ## Assessment One ungated Apache 2.0 model judges harm, jailbreaks, RAG groundedness, function-call errors and custom criteria, with signed weights and published evaluation code. It is trained and tested on English only, each call checks one criterion, the 4.1 prompt format differs from 3.x, and IBM's watsonx.ai lists only the deprecated 3.0 model. ## Facts | Field | Value | | --- | --- | | Vendor | IBM (https://www.ibm.com/granite) | | Kind | Model API | | Category | Guardrails & safety filters (https://www.anchorterminal.com/categories/guardrails) | | Transport | HTTP | | Auth | None · No account or key is needed to download or run the model. The Hugging Face repository is not gated. A vLLM or Ollama server has whatever authentication the owner adds. | | Pricing | Free (Free) · Free to download and run under the Apache 2.0 licence, with the owner's hardware as the cost. IBM's watsonx.ai lists only the earlier `ibm/granite-guardian-3-8b`, marked deprecated, at $0.0002 per 1,000 input or output tokens (checked 2026-10-08). Version 4.1 is not on that list. | | x402 | No · No x402, MPP or L402. Granite Guardian is a model the owner runs, with no payment route (checked 2026-10-08). | | Licence | Apache 2.0 for the weights and the repository | | Source | https://github.com/ibm-granite/granite-guardian | | Docs | https://www.ibm.com/granite/docs/models/guardian | | llms.txt | not found | | Last release | 2026-04-29 | | GitHub stars | 182 (as of 2026-10-08) | | Model | `ibm-granite/granite-guardian-4.1-8b`, 8,380,551,168 parameters in BF16 safetensors, fine-tuned from `ibm-granite/granite-4.1-8b`. `config.json` gives 131,072 positions | | Licence | Apache 2.0. IBM asks that derivatives put the maker's name before Granite and says the name is a registered trademark (https://www.ibm.com/granite/docs/model-standards/naming-guidance) | | Access | Not gated on Hugging Face. Also `ollama run granite4.1-guardian:8b` and IBM's GGUF builds | | Built-in criteria | Harm, social bias, jailbreaking, violence, profanity, sexual content, unethical behaviour. Context relevance, groundedness and answer relevance for RAG. Function-calling hallucination for agents | | Custom criteria | Any rule in natural language in the `### Criteria:` section. IBM calls this bring your own criteria and says such criteria need testing | | Input | A conversation whose last user message is a `` block with a think or no-think instruction, the criterion and a scoring schema. Documents go in `documents=` and tool schemas in `available_tools=` | | Output | `yes` or `no`. Think mode puts a reasoning trace in `` tags first | | Runtimes | `transformers` and vLLM in the card, Ollama and GGUF from IBM. The evaluation code asks for `vllm>=0.15.1` and `transformers>=4.52` and says an 8B model fits on one 80 GB GPU | | IBM's figures | Version 4.1 without thinking. Safety F1 0.79 across ten sets, LLM-AggreFact balanced accuracy 0.760, FC Reward Bench 0.79, IFEval multi-constraint 0.844 | | Languages | English only, per the model card | | Integrity | `model.sig` is a sigstore signature. IBM documents verification with `model-signing` and calls model signing experimental (https://www.ibm.com/granite/docs/model-standards/signature-verification) | | Hosted by IBM | watsonx.ai lists `ibm/granite-guardian-3-8b` only, marked deprecated, at $0.0002 per 1,000 tokens. Version 4.1 is not listed | | Support | Issues at github.com/ibm-granite/granite-guardian and the Hugging Face community tab. Security reports go to IBM PSIRT | | Capabilities | guard.moderation, guard.policy, guard.injection, guard.self-host | | Tags | model, open-weights, self-hosted, local, free, apache-2.0, judge, rag, python, ollama | | JSON | https://www.anchorterminal.com/api/v1/tools/granite-guardian.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 56 | 11.2 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 60 | 9.8 | | Agent ergonomics | 13% | 16.2 | 69 | 11.2 | | Security & auth | 14% | 17.5 | 58 | 10.2 | | Payments & pricing | 10% | 12.5 | 60 | 7.5 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 47 | 4.1 | | Transparency & trust (editorial 67, provenance 73) | 7% | 8.8 | 70 | 6.1 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **60.1 → C** | ### Why each score - Reliability 56: Scored on the local-software lines, since the owner runs the model. Weights are ungated on Hugging Face, IBM publishes GGUF builds and Ollama carries `granite4.1-guardian:8b`. The card's install line is `pip install transformers torch vllm` with no versions, and the evaluation code asks for `vllm>=0.15.1` and `transformers>=4.52` and names an 80 GB GPU. No Python version is stated (14 of 20). The repository has no CI workflow and no tests. Its `evaluation` folder reproduces the card's benchmark figures, which is public but is not run automatically (5 of 25). Fourteen items are open on GitHub. Five are automated dependency alerts, one is an outside pull request, and three usage problems from May to September 2025 (issues 28, 29 and 35, on a 3.2 error and on Ollama) are open with three to seven comments each. The 4.1 Hugging Face page has no open thread (14 of 25). Versions are named 3.0 to 4.1 with a Git tag each and dated What's New notes, but there is no changelog file, and 4.1 changed the prompt format from the `guardian_config` argument of the 3.x cookbooks to a `` block without a migration note (9 of 15). Released as 4.1 with no preview label. IBM calls model signing experimental (14 of 15). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 60: Read for a model the owner serves. There is no specification of its own. The contract is `chat_template.jinja`, the prompt strings in the card and a fixed `` answer, and vLLM or Ollama supply the HTTP route (8 of 25). www.ibm.com/granite/docs has no llms.txt (the path returns the docs home page). The model card and README are Markdown on Hugging Face and GitHub (5 of 10). The card states the intended use, eleven built-in criteria with definitions, English-only training, the need to test custom criteria, and points to the HAP-38M model for tighter latency (18 of 20). The answer is binary inside fixed tags, and documents and tool schemas have their own template arguments. The criterion is free text (10 of 15). Four code examples, two notebooks for 4.1 and an Ollama page. Nothing documents failure modes such as a missing score tag (10 of 15). Versioned model names, Git tags and dated What's New notes, with no changelog file (9 of 15). - Agent ergonomics 69: Read as a classifier an agent calls. Without thinking the answer is a yes or no in tags. Think mode adds a reasoning trace, and the card's examples allow 2,048 output tokens. Each call judges one criterion (19 of 25). The caller chooses think or no-think, the criterion, whether the last user or assistant turn is judged, and passes documents and tool schemas separately (17 of 20). The model has no error responses of its own and the 4.1 card documents no confidence value, so a caller parses tags from text (7 of 20). Calls are stateless and the examples set temperature to 0, so a check can be repeated safely (16 of 20). No gate and one `ollama run` command, but the prompt strings and parser must be copied from the card because no package ships them, and vLLM needs a GPU (10 of 15). - Security & auth 58: Read as software the owner runs. No account, key or token is needed to get or run the weights, so there is no secret to leak, and any server authentication is the owner's to add (14 of 30). A classifier with no write actions (15 of 20). It reads untrusted text by design and has a built-in jailbreaking criterion. The card says the model may be prone to adversarial attacks and that reasoning traces may contain unsafe content, with no mitigation guidance beyond keeping to the scoring mode (8 of 15). No call log of its own. Think mode gives a reason for each judgement (6 of 15). IBM's security.txt is valid and names PSIRT and HackerOne, the weights are safetensors with a sigstore signature and published verification steps, and dependency scanning was added to the repository on 19 August 2026. The repository has no `SECURITY.md` (issue 20, open since 9 February 2025), and five scanner alerts and an outside bypass report of 19 July 2026 (issue 46) have no reply (15 of 20). - Payments & pricing 60: Self-hosted rule. Nothing to buy for the model, and the Apache 2.0 licence allows commercial use at no charge (20). Free to run with no card (20). The weights are not gated, so an agent can fetch and run them with no sign-up (20). No payment protocol (0). IBM's watsonx.ai sells only the deprecated `ibm/granite-guardian-3-8b` at $0.0002 per 1,000 tokens, which is not the model graded here. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 47: Read for an open-weight model. The 4.1 weights date from 29 April 2026, 162 days before the check. The card and signature changed on 26 and 27 August 2026, which we do not count as a release (10 of 30). Main releases came in October and December 2024, February and August 2025 and April 2026. The last 90 days brought the evaluation code on 10 August and a cookbook refactor on 19 August, and no model (10 of 20). Maintainers merge their own pull requests within a day and closed the evaluation-code request (issue 26) on 10 August 2026 after 17 months. An outside pull request of 12 August, the bypass report of 19 July and the 4.2 question of 17 September have no reply (10 of 25). `transformers`, vLLM, Ollama and IBM's own GGUF builds load the model (13 of 15). Dependency scanning is on, its five alerts are open, and there is no CI (4 of 10). - Transparency & trust 70: Weights and repository are under the Apache 2.0 licence with no gate and no use policy attached (30 of 30). Inputs stay on the owner's hardware, so no privacy statement applies. Training data is described as hh-rlhf samples annotated at DataForce plus synthetic data, and the datasets are not released (issue 27, open since 28 March 2025) (22 of 30). No deprecation policy for the open weights. Older versions stay downloadable, and watsonx.ai marks its hosted 3.0 model deprecated (5 of 20). The weights carry no telemetry of their own, but we found no statement either way and downloads go through Hugging Face or Ollama (10 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (17 items): https://www.anchorterminal.com/fixes/granite-guardian.md (JSON https://www.anchorterminal.com/fixes/granite-guardian.json) ### What we couldn't check - The lead named version 3.3. Granite Guardian 4.1 8B (April 2026) is the current model, and the listing grades it. The lead's interface and licence were right. - unchecked: we did not run the model, so the install lines, GPU memory and whether current `transformers` and vLLM releases load `GraniteForCausalLM` are from IBM's pages only. - unchecked: who replied on issues 20, 28, 29 and 35 and when. The GitHub API allowance for this network ran out, so only comment counts were read. - unchecked: the date watsonx.ai withdraws `ibm/granite-guardian-3-8b`, and whether 4.1 is on Azure AI Foundry or Replicate. www.ibm.com/docs answered 403 and the partner lists were not read. - unchecked: IBM's Granite Trust portal, which the docs give as the home of its responsible AI material. - Whether a Guardian model based on Granite 4.2 is planned. Issue 54 asks and has no reply. - Issue 46 is an outside, unverified report against the 3.0-2B model prompted as a chat model, which is outside the scoring mode IBM prescribes. No deduction was taken. - The 4.1 card lists sexual content in its scope of use but not in its list of built-in criteria. IBM's docs page and the Ollama page list it. ### Sources - Granite Guardian 4.1 8B model card: (seen 2026-10-08) - Hugging Face model metadata (gating, downloads, parameters, last change): (seen 2026-10-08) - Hugging Face commit history for the model: (seen 2026-10-08) - Hugging Face community threads for the model: (seen 2026-10-08) - chat template: (seen 2026-10-08) - list of Granite Guardian models on Hugging Face: (seen 2026-10-08) - IBM's GGUF builds: (seen 2026-10-08) - repository, README, tags, cookbooks and evaluation code (shallow clone at commit 9698a42): (seen 2026-10-08) - repository issues and pull requests: (seen 2026-10-08) - issue 46, outside report of bypasses on 3.0-2B: (seen 2026-10-08) - issue 20, no SECURITY.md: (seen 2026-10-08) - IBM Granite Guardian docs: (seen 2026-10-08) - IBM docs on partners that run Granite: (seen 2026-10-08) - IBM docs on signature verification: (seen 2026-10-08) - IBM naming guidance and licence statement: (seen 2026-10-08) - Ollama library page: (seen 2026-10-08) - watsonx.ai foundation model list and prices: (seen 2026-10-08) - IBM security.txt: (seen 2026-10-08) - RDAP record for ibm.com: (seen 2026-10-08) ## Who's behind it (provenance 73/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | International Business Machines Corporation | 20/20 | | Domain age | ibm.com, registered 1986-03-19 (40 years) | 15/15 | | Endpoint on the vendor's domain | no hosted endpoint | n/a | | Terms of service | nothing hosted, so the Apache 2.0 for the weights and the repository licence stands in | 10/10 | | Privacy policy | nothing hosted, not scored | n/a | | Status page | not found | 0/10 | | Changelog | not found | 0/10 | | security.txt | valid | 10/10 | IBM's naming guidance for Granite names International Business Machines Corporation as the developer and trademark owner. The Apache 2.0 licence in the repository is the document that governs use of the weights, so it is recorded as the terms. The Hugging Face repository declares the same licence in its metadata and has no licence file of its own. No privacy policy governs the model, because the owner runs it and no input reaches IBM. The privacy field is left out. www.ibm.com/.well-known/security.txt is present with PSIRT, HackerOne and email contacts and expires on 8 November 2026. RDAP gives 19 March 1986 as the registration date of ibm.com. IBM hosts no endpoint for version 4.1 that we found, so there is no status page. The repository has no changelog file. Dated notes sit in the README under What's New. Weights are on huggingface.co under the ibm-granite organisation and the code is at github.com/ibm-granite/granite-guardian, both off ibm.com. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service**. Nothing is hosted by the vendor, so there are no terms of service to read. The Apache 2.0 for the weights and the repository licence stands in and the check scores in full. **Privacy policy**. Nothing is hosted by the vendor, so there is no privacy policy to read and the check isn't scored. ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - Weights are ungated on Hugging Face under the Apache 2.0 licence, with IBM's own GGUF builds and an Ollama library entry - Built-in criteria cover harm, social bias, jailbreaking, violence, profanity, sexual content, unethical behaviour, three RAG checks and function-call hallucination - A custom criterion is one natural-language sentence in the prompt, and the answer is `yes` or `no` inside `` tags - The repository's `evaluation` folder reproduces the card's benchmark figures for versions 3.0 to 4.1 - Weights carry a sigstore signature in `model.sig`, and IBM documents how to verify it ## Weaknesses - Trained and tested on English only, per the model card - Each call judges one criterion, so checking several risks takes several calls or a separate LoRA adapter built on the 3.2 model - Version 4.1 moved the criterion into a `` block in the last user message, where 3.x cookbooks pass `guardian_config` - The repository has no CI, no tests and no `SECURITY.md`, and an issue asking for one has been open since 9 February 2025 - The card's out-of-distribution safety F1 is 0.79 without thinking, below the 0.81 it reports for version 3.3 - IBM's watsonx.ai model list has only `ibm/granite-guardian-3-8b`, marked deprecated, so 4.1 has no hosted endpoint from IBM that we found ## Before you call it (notes for agents) 1. Append the `` block as the final user message, with the mode line, `### Criteria:` and `### Scoring Schema:`. Copy the strings from the model card, because no package builds them 2. Use the no-think instruction for gating and parse ``. Think mode writes a reasoning trace first, and the card's examples allow up to 2,048 output tokens 3. Treat `yes` as the criterion being met, which for built-in criteria means the risk is present. Treat a missing `` tag as a failed check 4. Pass retrieved text through `documents=` and tool schemas through `available_tools=` in `apply_chat_template`, not inside the message text 5. Under Ollama, set `num_ctx` in the request options. IBM's docs say the default context is short and long requests are truncated ## Connect Install: ```bash pip install transformers torch vllm ``` First request: ```bash curl http://localhost:11434/api/chat \ -d '{"model": "granite4.1-guardian:8b", "messages": [{"role": "user", "content": "Hello!"}]}' ``` ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | OpenAI Guardrails | B | 69.5 | 175 | guard.injection, guard.moderation, guard.policy, guard.self-host | no | https://www.anchorterminal.com/tools/openai-guardrails.md | | NVIDIA NeMo Guardrails | B | 68.4 | 202 | guard.injection, guard.moderation, guard.policy, guard.self-host | no | https://www.anchorterminal.com/tools/nemo-guardrails.md | | Lakera Guard (Check Point AI Guardrails) | C | 59.6 | 492 | guard.injection, guard.moderation, guard.policy, guard.self-host | no | https://www.anchorterminal.com/tools/lakera-guard.md | | Guardrails AI | D | 49.6 | 701 | guard.injection, guard.moderation, guard.policy, guard.self-host | no | https://www.anchorterminal.com/tools/guardrails-ai.md | | Google Cloud Model Armor | BB | 77.9 | 16 | guard.injection, guard.moderation, guard.policy | no | https://www.anchorterminal.com/tools/google-model-armor.md | | Amazon Bedrock Guardrails | BB | 74.8 | 62 | guard.injection, guard.moderation, guard.policy | no | https://www.anchorterminal.com/tools/amazon-bedrock-guardrails.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Granite Guardian 4.1 8B is the newest main model, fine-tuned from `ibm-granite/granite-4.1-8b` with 8,380,551,168 BF16 parameters. The card gives April 2026 as the release date (source: ) - The Hugging Face repository is not gated and showed 55,359 downloads in the last month, 212,264 in total and 48 likes. Its weights date from 29 April 2026, and the card and signature were updated on 26 and 27 August 2026 (source: ) - IBM's own figures for 4.1 without thinking are F1 0.79 on out-of-distribution safety sets, balanced accuracy 0.760 on LLM-AggreFact and 0.79 on FC Reward Bench. The same card gives 0.81, 0.761 and 0.74 for version 3.3 (source: ) - The model card says the model is trained and tested on English only, that custom criteria need testing, and that reasoning traces may contain unsafe content and may not be faithful (source: ) - The family on Hugging Face also has HAP classifiers of 38M and 125M parameters, 3.x models from 2B to 8B, LoRA adapters on 3.2 for harm categories, harm correction and factuality, and a Japanese toxicity model (source: ) - IBM publishes GGUF builds from Q2_K to bf16 in `ibm-granite/granite-guardian-4.1-8b-GGUF`, and Ollama's library has `granite4.1-guardian:8b` at 6.9GB with 31.2K downloads (source: ) - IBM's watsonx.ai model list has `ibm/granite-guardian-3-8b` only, marked deprecated, at $0.0002 per 1,000 tokens in and out (source: ) - The repository's `evaluation` folder, added on 10 August 2026, runs four benchmarks through vLLM and says an 8B model fits on a single 80 GB GPU (source: ) - A GitHub issue of 17 September 2026 asks whether a Guardian model will follow `granite-4.2-8b`. It had no reply on 8 October 2026 (source: ) ## Compare - [Amazon Bedrock Guardrails vs Granite Guardian](https://www.anchorterminal.com/compare/amazon-bedrock-guardrails-vs-granite-guardian.md): BB 74.8 vs C 60.1 - [Azure AI Content Safety (Prompt Shields) vs Granite Guardian](https://www.anchorterminal.com/compare/azure-ai-content-safety-vs-granite-guardian.md): C 60.7 vs C 60.1 - [Cisco AI Defense Inspection API vs Granite Guardian](https://www.anchorterminal.com/compare/cisco-ai-defense-inspection-vs-granite-guardian.md): C 61.3 vs C 60.1 - [Google Cloud Model Armor vs Granite Guardian](https://www.anchorterminal.com/compare/google-model-armor-vs-granite-guardian.md): BB 77.9 vs C 60.1 - [Granite Guardian vs LlamaFirewall](https://www.anchorterminal.com/compare/granite-guardian-vs-llamafirewall.md): C 60.1 vs D 50.8 - [Granite Guardian vs Guardrails AI](https://www.anchorterminal.com/compare/granite-guardian-vs-guardrails-ai.md): C 60.1 vs D 49.6 - [Granite Guardian vs Lakera Guard (Check Point AI Guardrails)](https://www.anchorterminal.com/compare/granite-guardian-vs-lakera-guard.md): C 60.1 vs C 59.6 - [Granite Guardian vs Llama Guard 4](https://www.anchorterminal.com/compare/granite-guardian-vs-llama-guard.md): C 60.1 vs D 49.1 - [Granite Guardian vs Mistral Moderation API](https://www.anchorterminal.com/compare/granite-guardian-vs-mistral-moderation.md): C 60.1 vs C 58.4 - [Granite Guardian vs NVIDIA NeMo Guardrails](https://www.anchorterminal.com/compare/granite-guardian-vs-nemo-guardrails.md): C 60.1 vs B 68.4 - [Granite Guardian vs OpenAI Guardrails](https://www.anchorterminal.com/compare/granite-guardian-vs-openai-guardrails.md): C 60.1 vs B 69.5 - [Granite Guardian vs OpenAI Moderation API](https://www.anchorterminal.com/compare/granite-guardian-vs-openai-moderation.md): C 60.1 vs BB 71.3 - [Granite Guardian vs Prisma AIRS AI Runtime Security API](https://www.anchorterminal.com/compare/granite-guardian-vs-prisma-airs.md): C 60.1 vs B 62.8 - [Granite Guardian vs Presidio](https://www.anchorterminal.com/compare/granite-guardian-vs-microsoft-presidio.md): C 60.1 vs B 66 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on ibm.com or one of its subdomains, or the README of github.com/ibm-granite/granite-guardian. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "granite-guardian", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Granite Guardian on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Granite Guardian on Anchor Terminal](https://www.anchorterminal.com/badges/granite-guardian.svg)](https://www.anchorterminal.com/tools/granite-guardian) ``` Plain link: ```html Granite Guardian on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Granite Guardian is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/granite-guardian-dark.png - Light: https://www.anchorterminal.com/assets/share/granite-guardian-light.png