I ran my event scanner on 18 open-source repos. Fourteen came back with two events or fewer, and six of those zeros were my fault.

Description and use

The event scanner CLI initially reported zero events in 14 of 18 repositories due to missing configs, nested wrappers, and other limitations. After addressing these gaps, event counts increased and test files were excluded.

Problem

A CLI event scanner reports zero analytics events in many repos, but the zero may be misleading because of scanner limitations or repo structure.

Outcome

Scanner initially missed many events due to missing TypeScript configs, helper wrappers, dollar-prefixed names, dynamic imports, and memory limits. After fixes, event counts rose significantly and test files were excluded from final counts.

Workflow

• Clone each repo shallowly
• Run event scanner with default settings
• Verify reported event counts by grepping source
• Identify scanner gaps (config, helpers, naming, dynamic imports, memory)
• Fix scanner to handle each gap
• Re-run scanner and compare counts

Evidence

Fourteen of the 18 came back with two events or fewer.

Source

After teaching it to read each app's own settings, and to find the repository's own packages by folder when nothing is installed, it reports 9.

Source

The CLI now starts itself with more memory when the repository is large and the machine can spare it.

Source