npmtraffic
Transparency
Infrastructure, hosting, and cost posture.
Hosting & Infrastructure
npmtraffic runs on Vercel and relies on api.npmjs.org for download data. Hosting costs are managed through minimal server-side logic and in-memory caching. There is no paid tier, so the project stays focused on reliability rather than monetization.
Caching & Freshness
We cache responses for ~15 minutes and allow stale buffering up to 24 hours for resilience. If the upstream npm API is unavailable, we may serve cached data (including stale) when available to avoid blank pages. Exports include cache/stale indicators in metadata for traceability.
Rate Limiting & Privacy
Public endpoints are rate limited to prevent abuse. Rate limiting uses request metadata transiently and is not used for profiling. We use privacy-friendly telemetry (Vercel Web Analytics) to understand basic site usage (aggregate page views and top pages) without cross-site tracking cookies or user profiles.
Local-first events & sharing
Event markers are stored in your browser storage by default. If you explicitly share a link that includes an events parameter, that payload is embedded in the URL and can be imported by others.