npm package reports / billion-context

What ships in billion-context?

billion-context@0.1.216 ships 46 files; 2 items worth a look.

“A context-compression plugin — small context windows (a 100K context is enough), 5x fewer tokens, month-long single sessions (billions of tokens), and compression quality — for all agents: pi, OpenCod”

0.1.216version
46files
47.2 MBunpacked
1.2Mweekly dl

Findings

2 additional matches for secret patterns or sensitive file types were not published here. Many are test fixtures or documentation examples; we never list details of possible credentials publicly. Maintainers can see the details with a live scan.

Keep it this way: check every release in CI

This report covers one published version. ReleaseShield runs on every publish. It scans the exact tarball (npm pack), wheel or Docker image your pipeline builds and fails the release before anything unexpected reaches the registry.

# .github/workflows/release.yml
- uses: my2ctyw8h6-hash/release-shield@v1
  with:
    fail-on: high
  env:
    RELEASESHIELD_TOKEN: ${{ secrets.RELEASESHIELD_TOKEN }}

See plans: from $19/mo Re-scan billion-context live

Maintainer? Show it in your README

The badge reflects the latest automated scan of the published tarball and refreshes on its own. ReleaseShield report for billion-context

[![ReleaseShield](https://release-shield-app.vercel.app/api/badge/npm/billion-context.svg)](https://release-shield-app.vercel.app/npm/billion-context?ref=badge)

Other package reports

chalk · @octokit/types · @inquirer/figures · progress · @ai-sdk/provider-utils · cli-truncate · fast-string-width · @inquirer/prompts · import-local · ansis · uglify-js · supports-hyperlinks

Automated heuristic scan of the public tarball for billion-context@0.1.216, run on 2026-11-21. Findings describe file contents and are not a judgment of the package's security or its maintainers; many are intentional. Maintainer and want this report removed or refreshed? Open an issue at github.com/my2ctyw8h6-hash/release-shield.