@things-factory/print-ui
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is an intra-org @things-factory package replacing a similar dep; consistent with normal maintenance. | ai | |
| dependencies | unvetted-dep:@things-factory/context-ui | AI (dependencies): Sibling package in the same @things-factory monorepo; unvetted status is expected for co-released packages. | ai | |
| dependencies | unvetted-dep:@things-factory/layout-base | AI (dependencies): Sibling package in the same @things-factory monorepo; unvetted status is expected for co-released packages. | ai | |
| provenance | no-provenance | AI (provenance): Long-lived org package; no provenance is consistent across all prior versions. | ai | |
| phantom-deps | phantom-dep:@things-factory/i18n-base | AI (phantom-deps): Same-org scoped dep in a monorepo; declared but used transitively is expected pattern here. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 9.2.24 | 4 / 0 | |
| 9.2.19 | 4 / 0 | |
| 9.2.16 | 4 / 0 | |
| 9.1.19 | 4 / 0 | |
| 8.0.88 | 4 / 0 | |
| 8.0.87 | 4 / 0 | |
| 8.0.75 | 4 / 0 | |
| 8.0.74 | 4 / 0 | |
| 8.0.64 | 4 / 0 | |
| 8.0.63 | 4 / 0 | |
| 4.3.815 | 4 / 0 | |
| 4.3.767 | 4 / 0 | |
| 4.3.764 | 4 / 0 | |
| 4.3.755 | 4 / 0 | |
| 4.3.752 | 4 / 0 | |
| 4.3.743 | 4 / 0 | |
| 4.3.740 | 4 / 0 | |
| 4.3.738 | 4 / 0 | |
| 4.3.734 | 4 / 0 | |
| 4.3.729 | 4 / 0 | |
| 4.3.727 | 4 / 0 | |
| 4.3.725 | 4 / 0 | |
| 4.3.723 | 4 / 0 | |
| 4.3.695 | 4 / 0 | |
| 4.3.689 | 4 / 0 |
v9.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.19
1 finding[Accepted risk] Package 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.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.74
2 findingsThis version was published by a different npm account than previous versions on 2026-01-02. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.63
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.3.815
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.767
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.3.764
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.755
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.3.752
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.3.743
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.740
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.738
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.3.734
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.3.729
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.727
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.725
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.723
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.3.695
2 findingsThis version was published by a different npm account than previous versions on 2025-11-21. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.689
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.