← Home

@saola.ai/replay

npm Repository Homepage

This package contains all the necessary code to replay recorded events. See the [guide](../../guide.md) for more info on rrweb.

7
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

eran.shahararkady.fukzondev.saolareemhagbidimafe

Keywords

rrweb@rrweb/replay

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Common for small-org forks; no other risk signals. ai
semgrep semgrep:base64-decode AI (semgrep): Base64 decode is part of upstream rrweb replay logic for encoding session data; not a malicious payload. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get usage is from upstream rrweb Proxy-based mirror implementation; standard pattern, not obfuscation. ai
phantom-deps phantom-dep:@saola.ai/rrweb-types AI (phantom-deps): Same-org scoped type-only dependency; types are consumed at build time, not imported at runtime. ai

Versions (showing 7 of 7)

Version Deps Published
2.0.28 2 / 5
2.0.27 2 / 5
2.0.26 2 / 5
2.0.25 2 / 5
2.0.24 2 / 5
2.0.23 2 / 5
2.0.22 2 / 5

v2.0.28

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.27

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.26

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.25

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.23

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.22

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.