← Home

@fiscozen/pdf-viewer

npm

Design System PdfViewer component

13
Versions
MIT
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

panicofralen_fiscozentrebhcbfiscozenfrancivagosergioterrasifiscozen

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:dist/pdf-viewer.js AI (source-diff): Base64-encoded OTF font used by PDF.js _loadTestFont for font-load detection; stable false positive for this package. ai
bogus-package bogus-package AI (bogus-package): Internal design system component; missing repo/keywords/README detail is expected for org-internal packages. ai
phantom-deps phantom-dep:@fiscozen/button AI (phantom-deps): Same-org dep; phantom detection is a false positive for bundled components. ai
phantom-deps phantom-dep:@tato30/vue-pdf AI (phantom-deps): Likely bundled into dist; phantom detection false positive for bundled deps. ai

Versions (showing 13 of 13)

Version Deps Published
1.0.5 3 / 18
1.0.4 3 / 18
1.0.3 3 / 18
1.0.2 3 / 18
1.0.1 3 / 18
1.0.0 3 / 18
0.1.6 2 / 18
0.1.5 2 / 18
0.1.4 2 / 18
0.1.3 2 / 18
0.1.2 2 / 18
0.1.1 1 / 18
0.1.0 1 / 18

v1.0.5

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: sergioterrasifiscozen → trebh (on 2026-07-17, known maintainer) provenance

This version was published by a different npm account (trebh) than the most recent previously approved version (sergioterrasifiscozen) on 2026-07-17, but trebh 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.

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v0.1.0

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.