Privacy policy
Last updated: November 20, 2026
apm is an open-source package registry and security scorer operated at apmjs.dev, registry.apmjs.dev, and docs.apmjs.dev. This page states what data we collect and why.
Browsing and API requests
You do not need an account to browse packages, install from the registry, or query the HTTP and MCP APIs. Our Cloudflare Workers handle incoming requests and record standard operational logs (status codes, latency, route labels, and error codes). Rate limiting hashes or keys requests by your network address (normalized to a /64 prefix for IPv6) inside Cloudflare.
We send privacy-preserving page views and server error events to Databuddy with no cookies, no referrer header, and no package names in page-view labels.
Accounts, sign-in, and second factors
When you sign in with GitHub OAuth, we store your GitHub numeric user ID, GitHub login, email address, and display name to bind your permanent @scope and manage sessions.
If you enroll an authenticator app (TOTP), passkey (WebAuthn), or recovery codes, we store the encrypted TOTP secret, passkey public key metadata, and hashed recovery codes. Session cookies are HttpOnly and restricted to apmjs.dev. CLI staging tokens are stored as SHA-256 hashes.
Published packages and public logs
Packages you publish to apm, their tarballs, metadata, security scores, yanks, revocations, and moderation events are public by design so installers can verify what they run.
Contact and deletion requests
To request account deletion or ask a privacy question, open an issue on github.com/opencoredev/apmjs or report security-sensitive matters privately through GitHub Security Advisories.