@things-factory/pdf
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @things-factory/pdf package; Levenshtein match to 'pg' is a false positive with no brand impersonation intent. | ai | |
| phantom-deps | phantom-dep:handlebars | AI (phantom-deps): handlebars is declared as a runtime dep and referenced in config; phantom-dep heuristic misfires here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 9.2.24 | 6 / 0 | |
| 9.2.19 | 6 / 0 | |
| 9.2.17 | 6 / 0 | |
| 8.0.88 | 6 / 0 | |
| 8.0.64 | 6 / 0 | |
| 8.0.63 | 6 / 0 |
v9.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.