@saola.ai/rrweb-snapshot
rrweb's component to take a snapshot of DOM, aka DOM serializer
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): fromBase64 is a documented utility in rrweb-snapshot for decoding CSS/data URIs; not a payload-hiding pattern. | ai | |
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): postcss is listed as a runtime dependency in package.json; phantom-dep heuristic misfires here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.0.28 | 1 / 12 | |
| 2.0.27 | 1 / 12 | |
| 2.0.26 | 1 / 12 | |
| 2.0.25 | 1 / 12 | |
| 2.0.24 | 1 / 12 | |
| 2.0.23 | 1 / 12 | |
| 2.0.22 | 1 / 12 |
v2.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.