updated 2026-11-11 00:08 UTC

deja-vu

Repository Website

Shared local memory, cross-agent handoff, and code recovery across 43 coding agents. One Go binary; every session stays on disk.

Memory & Knowledge Go Listed MIT

Is deja-vu safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 9.1 / 10
Provenance None
Signed commits 80%
Last push yesterday
Advisories None known
Compare deja-vu

How does it stack up against its Memory & Knowledge neighbours?

Pick any agent to compare →
Suggest a correction

In detail: deja-vu scores 78.2/100 (Grade B), ranked #222 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 9.1/10; 80% of recent commits are signed; no published advisory affects its latest release (@vshulcz/deja-vu); last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How deja-vu could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships deja-vu and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/vshulcz/deja-vu, MIT, last pushed 2026-11-10. 80% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Strong

    OpenSSF Scorecard rates the repository's practices 9.1/10 (scanned Nov 10, 2026). The checks that decide who can get a change released:

    • Code Review5
    • Branch Protectionn/a
    • Signed Releases6
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies10
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection -1
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 5
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 10
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 10
    SAST 10
    Security-Policy 10
    Signed-Releases 6
    Token-Permissions 10
    Vulnerabilities 10

  3. Published packages Linked, not attested

    • npm @vshulcz/deja-vu Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @vshulcz/deja-vu 0.24.1. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of deja-vu.

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues deja-vu’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How deja-vu compares in Memory & Knowledge

  1. #10 Vespa 84.0 +5.8
  2. #11 Mem0 82.4 +4.2
  3. #12 deja-vu 78.2 this agent
  4. #13 agentmemory 77.3 −0.9
  5. #14 FAISS 75.7 −2.5

Bars show each HVTrust score; the tick marks deja-vu’s 78.2.

Where the 78.2 comes from

HVTrust dimensions vs the Memory & Knowledge average

78.2 / 100 · 100.0% confidence

deja-vu Memory & Knowledge average (52 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
15.4 / 25
3.7 above avg 11.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.8 below avg 12.6
Transparency50% declared license · 50% OSSF Scorecard
16.2 / 17
3.3 above avg 12.9
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
2.6 above avg 17.3
AdoptionLog-scaled stars · package downloads
12.2 / 20
0.9 below avg 13.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-10
Newly Listed
First tracked at rank #219
Maintainer Checklist
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent
View Memory & Knowledge Report missing data
79.5
Activity sub-score · out of 100
#12
In Memory & Knowledge

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-11 00:08 UTC · Repo last pushed yesterday

Activity & Reach

Stars
1.5k
Forks
178
Last Push
2026-11-10
yesterday
Commits (4 wk)
488
Downloads (7d)
2,970
npm
HN mentions (30d)
—
Open Issues
6
Rank Change
▼3
was #219

Analysis

Activity Inputs

79.5 / 100
StarsRepository reach
19.0 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
10.5 / 20

Common questions about deja-vu

Public supply-chain signals for deja-vu are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but deja-vu carries less obvious unverified-evidence risk than projects with thin signals.
Does deja-vu publish package provenance?
No published build provenance is currently detected for deja-vu. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does deja-vu have an OpenSSF Scorecard?
deja-vu has an OpenSSF Scorecard score of 9.1/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is deja-vu actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does deja-vu use?
deja-vu ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are deja-vu's commits signed?
80% of the last 100 commits to deja-vu are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
deja-vu appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain deja-vu?

For maintainers

HVTrust scores deja-vu from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Listed 1
2026-11-10
Newly Listed
First tracked at rank #219
GitHub → Website → npm: @vshulcz/deja-vu

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 78.2 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/deja-vu.svg)](https://hvtracker.net/agents/deja-vu)
HTML:
<a href="https://hvtracker.net/agents/deja-vu"><img src="https://hvtracker.net/badge/deja-vu.svg" alt="HVTrust"></a>

Other agents in Memory & Knowledge

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON