Sentry Init — the init call you already ship, audited, hardened, and sized to your quota

Paste the Sentry initialisation your project already ships — JavaScript, TypeScript, Python, Go, Ruby, PHP, .NET or Java — and work it in one sitting across four lanes: audit the configuration option by option, harden what it sends about your users, size its sample rates to the quota you pay for, and name the monitoring signals it still cannot see. The free half runs in your browser: a parser for eight SDK syntaxes that normalises option names across platforms, DSN parsing that catches a legacy secret half, about thirty lint rules, credential masking before anything is sent, and the arithmetic that turns your traffic and your rates into a monthly event count — plus the rate that would fit your allowance. Built on @getsentry/sentry-sdk-setup, @getsentry/sentry-node-sdk, @getsentry/sentry-browser-sdk, @getsentry/sentry-nextjs-sdk, @getsentry/sentry-feature-setup and @getsentry/sentry-otel-exporter-setup.

Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.