PubLedge
NPM · PUBLEDGE · SCANNED AUG 3
Open recordkeeping protocol for JIAs, RMAs, no-action letters, and analogous instruments.
Available components
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 & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 632 tokens (~48/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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 · publedge
claude mcp add snapsynapse-publedge -- npx -y publedge
codex mcp add snapsynapse-publedge -- npx -y publedge
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"snapsynapse-publedge": {
"type": "local",
"command": [
"npx",
"-y",
"publedge"
],
"enabled": true
}
}
} openclaw mcp add snapsynapse-publedge --command npx --arg -y --arg publedge
mcp_servers:
snapsynapse-publedge:
command: "npx"
args: ["-y", "publedge"] {
"mcpServers": {
"snapsynapse-publedge": {
"command": "npx",
"args": [
"-y",
"publedge"
]
}
}
} 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.
- 3 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Jul 26 −12
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 +33
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- 26 Jul 26 29
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 0 packages
0 packages in the resolved dependency tree.
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.
fetch_by_url ~83
Fetch a legal instrument by its canonical URL (e.g. https://publedge.org/us/utah/oaip/rma/2025-001/ or /us/utah/oaip/rma/2025-001/). Returns the same payload as get_legal-instrument.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Canonical hierarchical URL or path. |
No output schema declared.
No examples provided.
get_authority ~41
Get a single authority by its ID. Returns all frontmatter fields and body content.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The authority ID (filename without .md) |
No output schema declared.
No examples provided.
get_legal-instrument ~45
Get a single legal instrument by its ID. Returns frontmatter, timeline, and provisions.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The legal instrument ID (filename without .md) |
No output schema declared.
No examples provided.
get_mappings ~20
All mapping entries connecting legal instruments to obligations via terms.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_matrix ~20
Coverage matrix showing which obligations are addressed by which legal instruments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_obligation ~41
Get a single obligation by its ID. Returns all frontmatter fields and body content.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The obligation ID (filename without .md) |
No output schema declared.
No examples provided.
get_recently_changed ~42
Return legal instruments sorted by last_verified or last changelog entry, most recent first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max results to return (default 20). |
No output schema declared.
No examples provided.
get_upcoming ~47
Return legal instruments with upcoming milestones (enacted, effective, expires dates in the future). Sorted by date ascending.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max results to return (default 20). |
No output schema declared.
No examples provided.
list_authorities ~17
List all authorities in the knowledge base.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_legal-instruments ~159
List legal instruments in the knowledge base. Optional filters: jurisdiction, authority, type, status. Returns id, title, status, authority, type, jurisdiction, and canonical url for each match.
| Name | Type | Req | Description |
|---|---|---|---|
| authority | string | — | Filter by authority slug (e.g. "utah-oaip", "cfpb"). |
| jurisdiction | string | — | Filter by jurisdiction slug (e.g. "us-ut", "us"). |
| status | string | — | Filter by status (e.g. "enforcing", "executed", "enacted"). |
| type | string | — | Filter by instrument type (e.g. "statute", "rma", "jia", "ao", "nal", "plr", "il"). |
No output schema declared.
No examples provided.
list_obligations ~28
List all obligations in the knowledge base. Returns id, title, and group for each.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search ~42
Full-text search across all entities in the knowledge base. Searches titles, IDs, and body content.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query (case-insensitive substring match) |
No output schema declared.
No examples provided.
search_obligations ~47
Search only within obligations (obligation titles, IDs, body text). Same query semantics as search but scoped.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query (case-insensitive substring match) |
No output schema declared.
No examples provided.