← Home

@zumer/snapdom

18
Versions
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

tinchox5

Keywords

zumerlabsnapDOMhtml2canvashtml2canvas alternativedom-to-image alternativehtml-to-imagescreenshotenginehtml capturedom capturehtml to imagedom to imagehtml screenshotcapture elementhtml snapshotelement screenshotweb capturesnapshot toolrender htmlcapture domweb snapshothtml exportdom snapshothtml to pnghtml to svg

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/preCache.mjs AI (source-diff): Standard esbuild minified bundle with clear header; stable for this package. ai
provenance no-provenance AI (provenance): Informational; no provenance is common and not a risk signal for this package. ai

Versions (showing 18 of 18)

Version Deps Published
2.22.0 0 / 9
2.18.0 0 / 8
2.16.0 0 / 8
2.15.0 0 / 8
2.12.9 0 / 8
2.12.8 0 / 8
2.12.2 0 / 8
2.12.1 0 / 8
2.12.0 0 / 8
2.9.0 0 / 7
2.8.0 0 / 7
2.7.0 0 / 7
2.6.0 0 / 7
2.5.0 0 / 7
2.1.0 0 / 7
2.0.2 0 / 7
2.0.1 0 / 7
2.0.0 0 / 7

v2.22.0

1 finding
INFO No provenance attestation provenance

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

v2.18.0

1 finding
INFO No provenance attestation provenance

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

v2.16.0

1 finding
INFO No provenance attestation provenance

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

v2.15.0

1 finding
INFO No provenance attestation provenance

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