The Index · Security

Qverisai vs Shieldcortex

These two are level on the tashan score (within 1 points), so the score does not decide it. The evidence rows below are where they differ. Both are measured the same way, on the same day, from public evidence only — so this is a comparison of two measurements rather than two marketing pages. How we measure ›

QverisaiShieldcortexwhat it means
tashan score7071upkeep + freshness, gated by adoption
Adoption evidence1k/wk3k/wkthe raw public signal the score came from
Last releaseactiveactivenpm publish or repo push
Upkeep8172cadence, maintainers, status
Expertise gradedeepsolidan LLM read of its own documentation against a fixed rubric
Security auditno known advisoriesno known advisories, runs an install script, no build provenancea summary — the full audit, free, is on each dossier
LicenceMIT
Maintainersmore than oneone primarybus-factor risk

Install either

Qverisai

claude mcp add qverisai-mcp -- npx -y @qverisai/mcp

Shieldcortex

claude mcp add shieldcortex -- npx -y shieldcortex

Neither score is a security verdict — "well maintained" and "nothing known is wrong" are different claims, which is why the audit is a separate row and never folded into the number. The full audit for each — the advisory ids, the version that fixes them and anything that runs at install time — is free on its own page: Qverisai · Shieldcortex.

All ranked Security ›

tashan Pro$6/mo

Both numbers above are today’s. Whichever you pick, the question that matters next is when it changes — and this page cannot know that. Pro keeps the series behind each capability, and names what to move to.

  • Every score since we started measuring, for any capability
  • The named replacement when something you run is dying — not just that it is
  • tashan doctor over the config you already have, on your machine

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