billion-context

A context-compression plugin for month-long single sessions (billions of tokens) and small context windows (a 100K context is enough), billion-context is all you need .

Agent Skills TypeScript Listed NOASSERTION

Is billion-context safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard No result
Provenance None
Signed commits 24%
Last push today
Advisories None known
Compare billion-context
Suggest a correction

In detail: billion-context scores 42.7/100 (Grade D), ranked #346 of 396 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 24% of recent commits are signed; no published advisory affects its latest release (billion-context); last pushed 2026-11-17. Every point is earned from checkable signals — never paid placement. How scoring works →

How billion-context 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.

Chain of custody

Scanners check what the code says. This traces who ships billion-context 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 Partly signed

    github.com/ranxianglei/billion-context, NOASSERTION, last pushed 2026-11-17. 24% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Not checked

    No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.

  3. Published packages Linked, not attested

    • npm billion-context 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: billion-context 0.1.215. No published advisory affects it (OSV, checked 2026-11-16).

Changes to this chain

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

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues billion-context’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.

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 billion-context compares in Agent Skills

  1. #344 Design Judge Skills 42.8 +0.1
  2. #345 Fable Method 42.8 +0.1
  3. #346 billion-context 42.7 this agent
  4. #347 Nopua 42.5 −0.2
  5. #348 Superdesign Skill 42.1 −0.6

Bars show each HVTrust score; the tick marks billion-context’s 42.7.

Where the 42.7 comes from

HVTrust dimensions vs the Agent Skills average

42.7 / 100 · 67.0% confidence

billion-context Agent Skills average (396 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.2 / 25
7.0 below avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.7 below avg 11.5
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.7 below 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.3 / 20
8.1 above avg 9.2

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-11-10
Newly Listed
First tracked at rank #337
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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.
86.3
Activity sub-score · out of 100
#346

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

Signals refreshed 2026-11-17 12:07 UTC · Repo last pushed today

Rank Trend

2026-11-10 2026-11-17

Activity & Reach

Stars
7.7k
Forks
619
Last Push
2026-11-17
today
Commits (4 wk)
3731
Downloads (7d)
900,122
npm
HN mentions (30d)
—
Open Issues
735
Rank Change
▲1
was #347

Analysis

Activity Inputs

86.3 / 100
StarsRepository reach
23.3 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.0 / 20

Common questions about billion-context

Public trust evidence for billion-context is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does billion-context publish package provenance?
No published build provenance is currently detected for billion-context. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does billion-context have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for billion-context. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is billion-context actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does billion-context use?
billion-context ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are billion-context's commits signed?
24% of the last 100 commits to billion-context 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
billion-context 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: 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 billion-context?

For maintainers

HVTrust scores billion-context 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.

Reputation Timeline

Signal history
Listed 1
2026-11-10
Newly Listed
First tracked at rank #337

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Skills

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