updated 2026-10-18 00:07 UTC

Context Mode

Repository Website

Context window optimization for AI coding agents. Sandboxes tool output (98% reduction), persists session memory, and enforces routing across 17 platforms via MCP + hooks.

Agent Skills TypeScript Listed NOASSERTION Source-available

Is Context Mode safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.3 / 10
Provenance None
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 66.9/100 (Grade B), ranked #45 of 385 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 3.3/10; recent commits are unsigned; no published advisory affects its latest release (context-mode); last pushed 2026-10-18. 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-10-18. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Weak

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

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • 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 -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • npm context-mode 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: context-mode 1.0.169. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

  • 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. #43 Human Review 67.0 +0.1
  2. #44 Jscpd 66.9 ±0
  3. #45 Context Mode 66.9 this agent
  4. #46 Thesvg 66.7 −0.2
  5. #47 nWave 66.7 −0.2

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

Where the 66.9 comes from

HVTrust dimensions vs the Agent Skills average

66.9 / 100 · 100.0% confidence

Context Mode Agent Skills average (385 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.1 / 25
3.8 below avg 7.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
11.3 / 17
0.8 below avg 12.1
Maintenance60% last-push freshness · 40% commit activity
18.7 / 20
4.7 above avg 14.0
AdoptionLog-scaled stars · package downloads
16.6 / 20
7.6 above avg 9.0

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.3/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Context Mode View Agent Skills Report missing data
88.5
Activity sub-score · out of 100
#45
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 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-10-18 00:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars
30.5k
Forks
2.2k
Last Push
2026-10-18
today
Commits (4 wk)
47
Downloads (7d)
24,651
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #45

Analysis

Activity Inputs

88.5 / 100
StarsRepository reach
26.9 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
21.0 / 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.
Context Mode has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Context Mode publish package provenance?
No published build provenance is currently detected for Context Mode. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Context Mode have an OpenSSF Scorecard?
Context Mode has an OpenSSF Scorecard score of 3.3/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
medium confidence
1 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.
  • browser
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-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 11Listed 2HVTrust 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1Surface 1
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)
2026-08-11
Newly Listed
First tracked at rank #14
GitHub → Website → npm: context-mode

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 66.9 Grade B
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