← Home

@saola.ai/rrweb-player

npm Repository Homepage

rrweb's replayer UI

6
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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:base64-decode AI (semgrep): Base64 decode in rrweb UMD bundle is for session data encoding, not payload hiding; stable upstream pattern. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get used in rrweb's mirror proxy pattern for DOM recording; benign and traceable to upstream source. ai
phantom-deps phantom-dep:@tsconfig/svelte AI (phantom-deps): Referenced in tsconfig, not imported at runtime; stable false positive for this build-tool package. ai
phantom-deps phantom-dep:@saola.ai/rrweb-packer AI (phantom-deps): Same-org dep likely used indirectly via replay; phantom-dep heuristic fires but not a real risk. ai

Versions (showing 6 of 6)

Version Deps Published
2.0.27 3 / 15
2.0.26 3 / 15
2.0.25 3 / 15
2.0.24 3 / 15
2.0.23 3 / 15
2.0.22 3 / 15

v2.0.27

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.26

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.25

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.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.