eagle-mem 4.10.0 → 4.10.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +30 -0
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -177,6 +177,36 @@ Install and update print the files/configs they intend to touch before they chan
177
177
 
178
178
  Uninstall removes Claude Code and Codex hook registrations, Eagle Mem instruction blocks, custom Claude statusline integration, and skill links. It backs up user config files before editing them and keeps `~/.eagle-mem/memory.db` unless you explicitly confirm data deletion.
179
179
 
180
+ ### Download Counts, Privacy, and Telemetry
181
+
182
+ npm download graphs are public registry aggregates, not user analytics. A download count means the npm registry served package tarballs. It does not tell package authors who downloaded the package, which project installed it, whether it was a human, or whether it became an active user.
183
+
184
+ Large single-day spikes can come from normal registry behavior:
185
+
186
+ - package mirrors and caches fetching a newly published version
187
+ - CI jobs, disposable containers, and build farms reinstalling dependencies
188
+ - bots and scanners that analyze public npm packages
189
+ - repeated installs during local testing or release verification
190
+
191
+ Eagle Mem does not add phone-home telemetry, install tracking, analytics beacons, or a hosted usage service. Runtime memory stays local in `~/.eagle-mem/memory.db` unless you explicitly choose to move or publish it yourself.
192
+
193
+ You can inspect the same public aggregate counts shown by npm with:
194
+
195
+ ```bash
196
+ curl https://api.npmjs.org/downloads/range/last-week/eagle-mem
197
+ curl https://api.npmjs.org/downloads/range/last-month/eagle-mem
198
+ ```
199
+
200
+ Use these numbers as directional popularity signals only. They are useful for spotting broad distribution patterns, but they are not a reliable count of users, installs, projects, or companies.
201
+
202
+ ### v4.10.1 Patch
203
+
204
+ This documentation patch clarifies npm download-count behavior and Eagle Mem privacy expectations:
205
+
206
+ - npm download counts are aggregate tarball-serving statistics.
207
+ - Package maintainers cannot identify who downloaded the package from npm's public stats.
208
+ - Eagle Mem remains local-first and does not include install telemetry or phone-home analytics.
209
+
180
210
  ### v4.10.0 Minor Release
181
211
 
182
212
  This release makes Eagle Mem broader and safer across agent workflows:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "eagle-mem",
3
- "version": "4.10.0",
3
+ "version": "4.10.1",
4
4
  "description": "Shared memory, release guardrails, RTK token protection, and worker lanes for Claude Code, Codex, and Grok",
5
5
  "bin": {
6
6
  "eagle-mem": "bin/eagle-mem"