@sentry/replay 0.2.0-13

User replays for Sentry

@sentry/replay@0.2.0-13 was published on 2022-05-31. Its manifest declares 5 runtime dependencies and 3 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All @sentry/replay versions · Permanent reference to 0.2.0-13 · Latest release

Package specifications

Version0.2.0-13
License declarationApache-2.0
Published2022-05-31T22:19:39.039Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count5
Peer requirement count3
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size161.18 KiB
Published file count36
Package typeNot declared
ES module entrydist/index.es.js
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies47
Repository stars8769
Repository forks1879

Install @sentry/replay 0.2.0-13

npm install @sentry/replay@0.2.0-13
pnpm add @sentry/replay@0.2.0-13
yarn add @sentry/replay@0.2.0-13

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained10/10 — 30 commit(s) and 24 issue activity found in the last 90 days -- score normalized to 10
Code-Review10/10 — all changesets reviewed
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
License10/10 — license file detected
Security-Policy10/10 — security policy file detected
Binary-Artifacts9/10 — binaries present in source code
Pinned-Dependencies2/10 — dependency not pinned by hash detected -- score normalized to 2
Branch-Protection4/10 — branch protection is not maximal on development and all release branches
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
Fuzzing0/10 — project is not fuzzed
SAST7/10 — SAST tool detected but not run on all commits

Evidence and freshness