# Community Growth Snapshot

Captured at: `2026-05-17T22:43:02.111Z`

This snapshot tracks the public signals for the `@bilig/headless` growth loop: GitHub conversion, npm demand, contributor on-ramp health, discussion activity, and traffic quality.

## GitHub

- Repository: [proompteng/bilig](https://github.com/proompteng/bilig)
- Stars: 23 / 1,000 (977 remaining)
- Forks: 17
- Watchers: 0
- Open issues: 17
- Default branch: `main`
- Topics: `agent-tools`, `ai-agents`, `excel`, `excel-formulas`, `formula-engine`, `formula-recalculation`, `headless-spreadsheet`, `mcp`, `mcp-server`, `model-context-protocol`, `nodejs`, `spreadsheet`, `spreadsheet-automation`, `spreadsheet-engine`, `spreadsheet-formulas`, `typescript`, `workbook-api`, `workbook-automation`, `xlsx`, `xlsx-recalculation`

## npm

- Package: `@bilig/headless@0.18.29`
- License: `MIT`
- Modified: `2026-05-17T22:39:39.796Z`
- Downloads last week: 17,235 (2026-05-10 to 2026-05-16)
- Downloads last month: 32,535 (2026-04-17 to 2026-05-16)

## Contributor Funnel

- Open good first issues: 15
- Open first-timers-only issues: 15
- Documentation starter issues: 6
- Non-documentation starter issues: 9
- Open help wanted issues: 15
- Open pull requests: 0
- External open issues: 0
- External open pull requests: 0
- External issues opened in the last 7 days: 6
- External pull requests opened in the last 7 days: 43

## Discussions

- Total discussions: 14
- #157 [Which Node workbook automation workflow should @bilig/headless prove next?](https://github.com/proompteng/bilig/discussions/157) (Ideas, 11 comments)
- #414 [Looking for one ugly workbook case to turn into a fixture](https://github.com/proompteng/bilig/discussions/414) (General, 1 comment)
- #270 [Show and tell: try @bilig/headless from npm in an empty Node project](https://github.com/proompteng/bilig/discussions/270) (Show and tell, 2 comments)
- #382 [How should headless spreadsheet engines handle stale XLSX cached values?](https://github.com/proompteng/bilig/discussions/382) (Ideas, 2 comments)
- #230 [Show and tell: MCP spreadsheet tool server for WorkPaper agents](https://github.com/proompteng/bilig/discussions/230) (Show and tell, 5 comments)

## Traffic

- Views: 602 from 189 unique visitors
- Clones: 28,427 from 3,596 unique cloners
- Top referrers: github.com (97/30), news.ycombinator.com (52/37), t.co (29/24), proompteng.github.io (17/10), Google (16/2)
- Top paths: /proompteng/bilig (250/161), /proompteng/bilig/issues (37/9), /proompteng/bilig/pulls (23/9), /proompteng/bilig/commits/main (15/1), /proompteng/bilig/tree/main/examples/headless-workpaper (12/7)

## External Discovery

- LibHunt indexes Bilig on the `headless-spreadsheet` topic page: <https://www.libhunt.com/topic/headless-spreadsheet>.
- That surface came from the May 7 Show HN discovery path and classifies the project near TypeScript, Spreadsheet, Excel, Agents, and `ai-agents` audiences.
- Keep GitHub repository topics, npm keywords, and proof-page copy aligned with `headless-spreadsheet`, `excel`, `ai-agents`, and formula-recalculation terms while waiting for crawler refreshes.

## Conversion Pressure

- Last-week npm downloads per current star: 749
- Last-month npm downloads per current star: 1,415
- Fourteen-day unique GitHub visitors per current star: 8
- Fourteen-day unique cloners per current star: 156
- Interpretation: these are pressure ratios, not attribution. High download or clone pressure with flat stars means the evaluator path needs a clearer proof, trust signal, or bookmark ask after verification.

## Spike Read

- The visible May 7-11 star jump still lines up with external developer traffic, not broad social posting.
- The strongest current external referrer is news.ycombinator.com with 52 views from 37 unique visitors.
- Hacker News is still ahead of X/t.co in qualified GitHub traffic: 52/37 versus 29/24.
- Replication plan: do not repost the same launch. Ship one sharper proof page, then ask HN/X/MCP audiences for a concrete adoption blocker: formula family, XLSX cache behavior, persistence shape, or agent writeback verification.

## Read This Snapshot

- Stars are the primary lagging goal; npm downloads, clone traffic, and external issues are leading signals.
- If downloads or clones rise without stars, improve README and npm star/bookmark conversion after proof blocks.
- If traffic comes from a channel but discussions stay quiet, switch from launch copy to a specific workflow-feedback ask.
- If the starter queue drops below three current issues, open scoped example tasks before the next distribution push.
