Is Recall · bledden safe and trustworthy?

tashan scores Recall · bledden on public evidence — tashan score 42.0/100, it is currently active, note: a single primary maintainer (bus-factor risk). Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Recall · bledden?

Configure it from its source repository — it is a remote / registry server.

Who maintains Recall · bledden?

1 GitHub contributors, source: bledden/claude-recall-plugin.

‹ The Index

Recall · bledden

plugin

Persistent conversation recall for Claude Code. Indexes every exchange into a local SQLite database so you can search, browse, and recover context at any time. Survives /clear commands and context compaction. Search across all sessions in a project or globally across every project. Auto-tags technical terms for discovery. Shares findings between parallel sessions via opt-in highlight connections. Includes a PostCompact nudge that automatically re-orients Claude after context loss. Optional proac

Works with: Claude Code (native)
native: this artifact type is that client's own format

Work: Knowledge management

Who it is for: Operations · Researcher

Install (Claude Code):

/plugin marketplace add anthropics/claude-plugins-community
/plugin install recall@claude-community

solid

“40 worked examples; short of deep on per-tool docs; read with 1 linked doc(s)”

This grade is wrong ›

tashan score: 42.0
Instruction depth: 70.0 (solid — documents the job properly, with examples you could follow)
Adoption: 1 repos
Upkeep: 56.0
Freshness: 81.0
Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
Health: active
GitHub stars: 22
Contributors: 1
License: MIT

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Recall · bledden scores 42 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/plugin-bledden-claude-recall-plugin-recall.svg)](https://tashan.sh/capability/plugin-bledden-claude-recall-plugin-recall.html)

source ↗ · plugin:bledden/claude-recall-plugin/recall

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?