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 .
Is billion-context safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare billion-context
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →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.
- Raise the OSSF Scorecard to 9.0no OSSF Scorecard result yet +38.1 → 80.8 A · #22 of 396
- Publish build provenance for its packagesnpm publish --provenance from CI +34.0 → 76.7 B · #27 of 396
- Sign every commit24% signed today +2.6 → 45.3 D · #323 of 396
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.
-
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.
-
Review and release Not checked
No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.
-
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.
-
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
- #344 Design Judge Skills 42.8 +0.1
- #345 Fable Method 42.8 +0.1
- #346 billion-context 42.7 this agent
- #347 Nopua 42.5 −0.2
- #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% confidencebillion-context Agent Skills average (396 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
86.3 / 100Common questions about billion-context
Does billion-context publish package provenance?
Does billion-context have an OpenSSF Scorecard?
Is billion-context actively maintained?
What license does billion-context use?
Are billion-context's commits signed?
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
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 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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/billion-context)
<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
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