Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Un-Default

NPM · ANTI-DEFAULT · SCANNED AUG 16

Inclusive language scan/fix for AI and human copy. Local rules, no account.

Available components

72 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to NomadBuilder/anti-default). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 256 tokens (~85/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage82
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 45% of tool parameters carry a description.Partial
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · anti-default

# add to Claude Code
claude mcp add nomadbuilder-un-default -- npx -y anti-default
# add to Codex CLI
codex mcp add nomadbuilder-un-default -- npx -y anti-default
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nomadbuilder-un-default": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "anti-default"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nomadbuilder-un-default --command npx --arg -y --arg anti-default
# ~/.hermes/config.yaml
mcp_servers:
  nomadbuilder-un-default:
    command: "npx"
    args: ["-y", "anti-default"]
// mcp.json
{
  "mcpServers": {
    "nomadbuilder-un-default": {
      "command": "npx",
      "args": [
        "-y",
        "anti-default"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 16 Aug 26 72

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 16 Aug 2026 · Analysed npm/anti-default@0.5.4

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo NomadBuilder/anti-default
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/NomadBuilder/anti-default/.github/workflows/publish.yml@refs/tags/v0.5.4
Rekor log index 2481518390
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:c73d3f377c19abe20f46efc2d317c19d0c0e887698b8229182a8c7863d4fce3df75ebc5f55a4aa0df4a2661a302c17e55cfc4d2abcce0d542b2e617a4
Dependencies 0 packages
Packages resolved 0
Tree resolution Complete
MCP tools · 3 exposed · ~256 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
un_default_feedback ~86

Record that a finding was fine in context (or a false positive). Suppresses it locally and writes structured feedback that can improve the shared catalog.

NameTypeReqDescription
contextstringyes
kindstringDefault: fine_in_context
matchstringyes
notestring
ruleIdstringyes
sourcestring

No output schema declared.

No examples provided.

un_default_fix ~79

Apply only safe, unambiguous 1:1 inclusive-language swaps (e.g. policeman→police officer, whitelist→allowlist). Does not touch coded/dogwhistle or soft contextual hits. Prefer dryRun first.

NameTypeReqDescription
dryRunbooleanIf true, report swaps without writing files
pathsarray

No output schema declared.

No examples provided.

un_default_scan ~91

Scan files for inclusive-language defaults in AI-generated or human copy. Returns JSON findings. Use after editing UI text, docs, READMEs, or marketing copy.

NameTypeReqDescription
changedFromstringOptional git ref — only scan files changed since it
failOnstringWhether remaining findings should be treated as blocking
pathsarrayPaths to scan (default: ["."])

No output schema declared.

No examples provided.