@fiscozen/pdf-viewer
Design System PdfViewer component
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.0.2
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (panicofr) than the most recent previously approved version (sergioterrasifiscozen) on 2026-06-09, but panicofr 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.1
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (francivago) than the most recent previously approved version (sergioterrasifiscozen) on 2026-05-07, but francivago 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.0
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (francivago) than the most recent previously approved version (sergioterrasifiscozen) on 2026-05-04, but francivago 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.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.