← Home

@sailfish-rrweb/rrweb-player

npm Repository Homepage

@sailfish-rrweb/rrweb's replayer UI

8
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

sailfishai

Keywords

@sailfish-rrweb/rrweb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@tsconfig/svelte AI (phantom-deps): Build-time tsconfig dependency; not imported at runtime, stable false positive. ai
phantom-deps phantom-dep:@sailfish-rrweb/packer AI (phantom-deps): Same-org scoped package; phantom-dep heuristic fires but it's a legitimate runtime dep. ai

Versions (showing 8 of 8)

Version Deps Published
0.38.0 3 / 15
0.5.10 3 / 15
0.5.9 3 / 15
0.5.8 3 / 15
0.2.5 3 / 15
0.2.4 3 / 15
0.2.3 3 / 15
0.1.3 3 / 15

v0.38.0

1 finding
LOW No provenance attestation provenance

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

v0.2.5

1 finding
LOW No provenance attestation provenance

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

v0.2.4

1 finding
LOW No provenance attestation provenance

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

v0.2.3

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.

v0.1.3

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.