← Home

@saola.ai/record

npm Repository Homepage

This package contains all the record related code in rrweb. See the [guide](../../guide.md) for more info on rrweb.

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@rrweb/record

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:base64-decode AI (semgrep): Fires in rrweb upstream UMD bundle; standard base64 decode utility, not malicious payload handling. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get usage is from rrweb upstream Proxy handler; standard pattern, not evasion. ai
phantom-deps phantom-dep:@saola.ai/rrweb-types AI (phantom-deps): Same org scope; types-only dep likely used at build time, not directly imported at runtime. ai
phantom-deps phantom-dep:@saola.ai/rrweb-utils AI (phantom-deps): Same org scope; bundled into UMD output rather than directly imported in source. ai

Versions (showing 6 of 6)

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

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. 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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.