Reuse Before Generate
NPM · REUSE-BEFORE-GENERATE · SCANNED AUG 3
Checks whether your idea already exists before your agent builds it. Searches GitHub, npm, Python.
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 Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), 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 (95 of 99), 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 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability26
- AI-judged instruction clarity (poor).Fail
- Context-footprint check failed: tool/resource definitions use about 487 tokens (~487/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 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
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.
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 · reuse-before-generate
claude mcp add aradar46-reuse-before-generate -- npx -y reuse-before-generate
codex mcp add aradar46-reuse-before-generate -- npx -y reuse-before-generate
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aradar46-reuse-before-generate": {
"type": "local",
"command": [
"npx",
"-y",
"reuse-before-generate"
],
"enabled": true
}
}
} openclaw mcp add aradar46-reuse-before-generate --command npx --arg -y --arg reuse-before-generate
mcp_servers:
aradar46-reuse-before-generate:
command: "npx"
args: ["-y", "reuse-before-generate"] {
"mcpServers": {
"aradar46-reuse-before-generate": {
"command": "npx",
"args": [
"-y",
"reuse-before-generate"
]
}
}
} 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 +37
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: unverified → poor ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 −6
- 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 −18
- Malware scan: pass → unverified ▼ security
- 28 Jul 26 +16
- Dependency health: partial → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: unverified functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- 27 Jul 26 26
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 95 packages
95 packages in the resolved dependency tree · 95 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.
check_before_building ~487
Run this BEFORE scaffolding a new project or a substantial new module. Searches GitHub, npm, and Python repos for existing projects that already do what's being proposed and filters out abandoned/unmaintained results. Returns verified-maintained candidates plus scoring instructions — the calling agent (you) must then judge semantic relevance itself and present at most 3 real alternatives with a concrete 'extend this instead of rebuilding' suggestion for each, per the returned instructions. REQUIRES you to supply `keywords` yourself (see its field description) — do not guess this tool can extract good search terms on its own; generic terms like 'mcp'/'agent'/'server' will bury results in noise.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Plain-language description of the project/module about to be built — what it does, not how. The more specific, the better the match quality. |
| keywords | array | yes | REQUIRED: 3-4 precise search terms YOU infer from the description, using your own understanding of what the user actually means — do this especially when the description is vague, informal, or from a… |
No output schema declared.
No examples provided.