npm/@wildcard-ai/deepcontext
graded version 0.1.15 · litmus-v12 · 2026-07-03
Adoption 32/100 · 446 npm/mo · as of 2026-07-04
- C-01 Tool-output injection
- pass
- C-02 Permission / egress overreach
- pass
- C-03 Sensitive-data handling
- pass
- C-04 Adversarial-input handling
- fail
tool-defs fingerprint · 0xde6582…5ffa9
Why D: Adversarial input handling failed (C-04): the server crashed, leaked internals (a stack trace), or amplified hostile input. No injection or data leak, so the grade caps at D.
Guided remediation — the specific changes that clear this grade.
Watch for new-version regrades
This grade is a snapshot of 0.1.15. Get an email when npm/@wildcard-ai/deepcontext ships a new version and polygraph re-runs the litmus on it — one message per new version, one-click unsubscribe.
Monitor this serverAdoption signals
The 32 / 100 adoption score blends the raw signals below — downloads, stars, dependents and release velocity — normalized across every tracked server. It measures reach, not safety; the litmus grade is the safety verdict. See the methodology.
- npm downloads (30d)
- 446
- Dependents (deps.dev)
- 2
- Last published
- 2025-09-22
Reproduce this grade
The harness is open and deterministic. Re-run it against the same server and compare the grade and fingerprint — a false grade is falsifiable, not merely disputable.
npx -p @polygraphso/litmus polygraphso-litmus npm/@wildcard-ai/deepcontextEmbed this badge
Drop it in a README, docs site, or package page. It always shows the current published grade and links back here.
[](https://polygraph.so/mcp/npm/@wildcard-ai/deepcontext)<a href="https://polygraph.so/mcp/npm/@wildcard-ai/deepcontext"><img src="https://polygraph.so/api/badge?server=npm/@wildcard-ai/deepcontext" alt="polygraph grade"></a>[](https://polygraph.so/mcp/npm/@wildcard-ai/deepcontext)Questions
- What does polygraph's D grade mean for npm/@wildcard-ai/deepcontext?
- It’s a behavioral grade on an A–F scale. polygraph connected to npm/@wildcard-ai/deepcontext the way an agent would, exercised its tools, and watched what it did — whether it tried to hijack the caller, send data off-box, leak planted secrets, or mishandle adversarial input. D is where that evidence placed it. It describes behavior on the day it ran, not a guarantee.
- What did polygraph test?
- Four probe categories, run against the live server in a sandbox: C-01 tool-output injection, C-02 permission and egress overreach, C-03 sensitive-data handling, and C-04 adversarial-input handling. The full battery is in the methodology.
- How do I reproduce this grade?
- Run
npx -p @polygraphso/litmus polygraphso-litmus npm/@wildcard-ai/deepcontext. The harness is open and deterministic, so anyone can re-run it against the same server and disprove a false grade — reproducibility is what the grade rests on. - Can a server pay polygraph for a better grade?
- No. Independence is disclosure-based: material support must be publicly registered, and no graded party gets review or approval rights over its letter. The grade is set by the evidence, not the relationship.