@push.rocks/smartpdf
A library for creating PDFs dynamically from HTML or websites with additional features like merging PDFs.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@push.rocks/smartfile | AI (dependencies): Same trusted publisher namespace; consistent with lossless/push.rocks ecosystem pattern. | ai | |
| dependencies | unvetted-dep:@push.rocks/smartdelay | AI (dependencies): Same trusted publisher namespace; consistent with lossless/push.rocks ecosystem pattern. | ai | |
| dependencies | unvetted-dep:@push.rocks/smartnetwork | AI (dependencies): Same trusted publisher namespace; consistent with lossless/push.rocks ecosystem pattern. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all push.rocks packages; publisher has clean track record. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): express is a runtime dep; @types/express is a type companion, not a phantom dep concern. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.2.2 | 13 / 7 | |
| 4.2.1 | 13 / 7 | |
| 4.2.0 | 13 / 5 | |
| 4.1.3 | 14 / 5 | |
| 4.1.1 | 14 / 5 | |
| 4.0.0 | 13 / 5 |
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.