updated 2026-11-10 04:07 UTC

Context Mode

Repository Website

Free, local plugin that keeps tool output out of your coding agent's context window. Sandbox and SQLite FTS5 search, 99% fewer bytes in context. Works with Claude Code, Codex, Pi, OpenCode, Gemini CLI, Copilot CLI and 4 more agents. Zero telemetry.

Agent Skills JavaScript Listed NOASSERTION Source-available

Is Context Mode safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 4.1 / 10
Provenance Attested
Signed commits 0%
Last push today
Advisories None known
Compare Context Mode

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Context Mode scores 84.8/100 (Grade A), ranked #11 of 384 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.1/10; recent commits are unsigned; no published advisory affects its latest release (context-mode); last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Context Mode 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 Context Mode 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 and, for skills, AST02 Supply Chain Compromise.

  1. Source Unsigned

    github.com/mksglu/context-mode, NOASSERTION, last pushed 2026-11-10. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Mixed

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

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 9
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages Linked and attested

    • npm context-mode Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: context-mode 2.1.7. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-11-05 Package provenance attestation detected
  • 2026-09-03 OSSF Scorecard: 3.3/10

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 Context Mode’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 the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Context Mode compares in Agent Skills

  1. #9 MisakaNet 86.6 +1.8
  2. #10 Claudecodeui 85.1 +0.3
  3. #11 Context Mode 84.8 this agent
  4. #12 Oh My Claudecode 84.8 ±0
  5. #13 DSH TUI 84.5 −0.3

Bars show each HVTrust score; the tick marks Context Mode’s 84.8.

Where the 84.8 comes from

HVTrust dimensions vs the Agent Skills average

84.8 / 100 · 100.0% confidence

Context Mode Agent Skills average (384 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.6 / 25
4.4 above avg 8.2
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.6 above avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
12.0 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
6.0 above avg 14.0
AdoptionLog-scaled stars · package downloads
17.0 / 20
7.9 above avg 9.1

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-11-05
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-11-05
Provenance Added
Package provenance attestation detected
2026-11-05
Grade Changed
Trust grade B → A
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.1/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent
View Agent Skills Report missing data
92.8
Activity sub-score · out of 100
#11
In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A 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-10 04:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
33.8k
Forks
2.3k
Last Push
2026-11-10
today
Commits (4 wk)
2251
Downloads (7d)
40,914
npm
HN mentions (30d)
—
Open Issues
20
Rank Change
=
was #11

Analysis

Activity Inputs

92.8 / 100
StarsRepository reach
27.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.6 / 20

Common questions about Context Mode

Source-available software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. Context Mode may have internal security practices not visible through public signals.
Public supply-chain signals for Context Mode are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Context Mode carries less obvious unverified-evidence risk than projects with thin signals.
Does Context Mode publish package provenance?
Yes. Context Mode's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Context Mode have an OpenSSF Scorecard?
Context Mode has an OpenSSF Scorecard score of 4.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 Context Mode actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Context Mode use?
Context Mode ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Context Mode's commits signed?
0% of the last 100 commits to Context Mode 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
Context Mode appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
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
How this surface has changed

Detected changes to Context Mode's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-11-05
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-11-05
Provenance Added
Package provenance attestation detected
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Context Mode?

For maintainers

HVTrust scores Context Mode 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
Rank 12HVTrust 3Grade 3Surface 2Scorecard 1Delisted 1Listed 1MCP 1Surface 1Provenance 1
2026-11-05
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-11-05
Provenance Added
Package provenance attestation detected
2026-11-05
Grade Changed
Trust grade B → A
2026-11-05
Rank Moved
Rank rose 23 spots (#40 → #17)
2026-11-05
HVTrust Changed
HVTrust up 14.5pts (68.2 → 82.7)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 218 spots (#267 → #49)
2026-09-23
HVTrust Changed
HVTrust up 35.1pts (31.1 → 66.2)
2026-09-22
Newly Listed
First tracked at rank #267
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-05
Rank Moved
Rank dropped 11 spots (#28 → #39)
2026-09-03
Scorecard Added
OSSF Scorecard: 3.3/10
2026-09-03
Grade Changed
Trust grade D → B
2026-09-03
Rank Moved
Rank rose 189 spots (#213 → #24)
2026-09-03
HVTrust Changed
HVTrust up 24.8pts (41.6 → 66.4)
2026-09-02
Rank Moved
Rank dropped 10 spots (#203 → #213)
2026-09-01
Rank Moved
Rank dropped 16 spots (#187 → #203)
2026-08-31
Rank Moved
Rank dropped 17 spots (#170 → #187)
2026-08-30
Rank Moved
Rank dropped 31 spots (#139 → #170)
2026-08-29
Rank Moved
Rank dropped 34 spots (#105 → #139)
2026-08-28
Rank Moved
Rank dropped 21 spots (#84 → #105)
2026-08-27
Rank Moved
Rank dropped 21 spots (#63 → #84)
2026-08-26
Rank Moved
Rank dropped 47 spots (#16 → #63)
GitHub → Website → npm: context-mode

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 84.8 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/context-mode.svg)](https://hvtracker.net/agents/context-mode)
HTML:
<a href="https://hvtracker.net/agents/context-mode"><img src="https://hvtracker.net/badge/context-mode.svg" alt="HVTrust"></a>

Other agents in Agent Skills

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