io.github.dingdawg/dingdawg-loop
NPM · DINGDAWG-LOOP · SCANNED AUG 3
Safe scheduled AI agents with governance gates. Verified, receipted, fail-closed.
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 Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
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 (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 576 tokens (~96/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 · dingdawg-loop
claude mcp add dingdawg-dingdawg-loop -- npx -y dingdawg-loop
codex mcp add dingdawg-dingdawg-loop -- npx -y dingdawg-loop
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dingdawg-dingdawg-loop": {
"type": "local",
"command": [
"npx",
"-y",
"dingdawg-loop"
],
"enabled": true
}
}
} openclaw mcp add dingdawg-dingdawg-loop --command npx --arg -y --arg dingdawg-loop
mcp_servers:
dingdawg-dingdawg-loop:
command: "npx"
args: ["-y", "dingdawg-loop"] {
"mcpServers": {
"dingdawg-dingdawg-loop": {
"command": "npx",
"args": [
"-y",
"dingdawg-loop"
]
}
}
} 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.
- 2 Aug 26 +48
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Schema quality: unverified → excellent ▲ functional
- Stability: unverified → 0.23 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 +4
- Malware scan: pass → unverified ▼ security
- Tool coverage: unverified → 100 ▲ functional
- 29 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
First indexed and scored.
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 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
execute_loop ~93
Manually trigger a loop execution. ALWAYS runs the governance gate first — if governance denies or errors, the loop body does NOT execute. Returns the governance receipt and execution outcome. This is the core DDLP safety mechanism: declare intent, get governed, then act.
| Name | Type | Req | Description |
|---|---|---|---|
| execution_notes | string | — | Optional notes about why this manual execution was triggered |
| loop_id | string | yes | The loop_id returned from register_loop |
No output schema declared.
No examples provided.
list_loops ~56
List all registered loops with their current status, schedule, risk tier, and last execution result. Use this to see what loops exist and their governance health.
| Name | Type | Req | Description |
|---|---|---|---|
| status_filter | string | — | Filter by loop status (default: all) |
No output schema declared.
No examples provided.
loop_audit ~73
Get the execution history for a specific loop. Shows every governance decision, outcome, and timestamp. Use this to audit how a loop has been behaving over time.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Maximum number of execution records to return (default: 20) |
| loop_id | string | yes | The loop_id to audit |
No output schema declared.
No examples provided.
pause_loop ~70
Pause a loop so it cannot be executed. Paused loops reject execute_loop calls until resumed. Use this to safely stop a loop without deleting its history.
| Name | Type | Req | Description |
|---|---|---|---|
| loop_id | string | yes | The loop_id to pause |
| reason | string | — | Why this loop is being paused (recorded in metadata) |
No output schema declared.
No examples provided.
register_loop ~245
Register a scheduled agent loop. Stores the loop definition with its cron schedule, action type, and risk tier. The loop is created in 'active' status but does NOT auto-execute in v1 — use execute_loop to trigger manually. The schedule is stored for v2 daemon support.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | yes | Type of action this loop performs (e.g., 'send_email', 'generate_report', 'sync_data', 'health_check') |
| description | string | yes | Detailed description of what this loop does each cycle. Be specific — governance evaluates this text. |
| metadata | object | — | Optional key-value metadata (e.g., owner, team, target_system) |
| name | string | yes | Human-readable name for this loop (e.g., 'daily-report-sender', 'hourly-health-check') |
| risk_tier | string | yes | Risk tier — determines governance gate strictness. 'critical' loops will almost always require human review. |
| schedule | string | yes | Cron expression for the schedule (e.g., '0 9 * * *' for daily at 9am, '@hourly'). Stored but not auto-executed in v1. |
No output schema declared.
No examples provided.
resume_loop ~39
Resume a paused loop so it can be executed again. Clears the pause reason from metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| loop_id | string | yes | The loop_id to resume |
No output schema declared.
No examples provided.