← Home

@edgepdf/web-runtime

npm Repository Homepage

EdgePDF Web Runtime — self-contained HTML viewer bundle for rendering PDF tile maps in WebView environments

16
Versions
SEE LICENSE IN LICENSE
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

admin_etdhaval_et

Keywords

pdfviewerwebviewpmtilesofflineruntimehtml

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@edgepdf/types AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic fires because it's re-exported rather than directly imported. ai
phantom-deps phantom-dep:@edgepdf/viewer-js AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic fires because it's re-exported rather than directly imported. ai

Versions (showing 16 of 16)

Version Deps Published
0.6.2 2 / 3
0.5.11 2 / 3
0.5.5 2 / 3
0.5.4 2 / 3
0.5.3 2 / 3
0.5.2 2 / 3
0.5.1 2 / 3
0.5.0 2 / 3
0.4.6 2 / 3
0.4.5 2 / 3
0.4.4 2 / 3
0.4.3 2 / 3
0.4.2 2 / 3
0.4.1 2 / 3
0.4.0 2 / 3
0.3.11 2 / 3

v0.6.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: dhaval_et → admin_et (on 2026-06-30, known maintainer) provenance

This version was published by a different npm account (admin_et) than the most recent previously approved version (dhaval_et) on 2026-06-30, but admin_et is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.5.11

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: admin_et → dhaval_et (on 2026-05-18, known maintainer) provenance

This version was published by a different npm account (dhaval_et) than the most recent previously approved version (admin_et) on 2026-05-18, but dhaval_et is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.