@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, so a manually published version cannot be tied back to a reviewed commit.
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 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 9.2.33 | 4 / 0 | |
| 9.2.30 | 4 / 0 | |
| 9.2.29 | 4 / 0 | |
| 9.2.24 | 4 / 0 | |
| 9.2.19 | 4 / 0 | |
| 9.2.17 | 4 / 0 | |
| 9.2.16 | 4 / 0 | |
| 9.2.13 | 4 / 0 | |
| 9.2.5 | 4 / 0 | |
| 9.1.19 | 4 / 0 | |
| 9.1.13 | 4 / 0 | |
| 9.1.0 | 4 / 0 | |
| 9.0.41 | 4 / 0 | |
| 9.0.36 | 4 / 0 | |
| 9.0.34 | 4 / 0 | |
| 9.0.25 | 4 / 0 | |
| 9.0.24 | 4 / 0 | |
| 9.0.20 | 4 / 0 | |
| 9.0.5 | 4 / 0 | |
| 9.0.2 | 4 / 0 | |
| 9.0.0 | 4 / 0 | |
| 8.0.88 | 4 / 0 | |
| 8.0.87 | 4 / 0 | |
| 8.0.86 | 4 / 0 | |
| 8.0.75 | 4 / 0 | |
| 8.0.74 | 4 / 0 | |
| 8.0.64 | 4 / 0 | |
| 8.0.63 | 4 / 0 | |
| 6.4.10 | 4 / 0 | |
| 6.4.8 | 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.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.13
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (heartyoh) than the most recent previously approved version (nalshya113) on 2026-03-19, but heartyoh 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.
v9.2.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nalshya113) than the most recent previously approved version (wengliang95) on 2026-03-06, but nalshya113 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.
v9.1.13
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nalshya113) than the most recent previously approved version (heartyoh) on 2025-10-22, but nalshya113 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.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.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.
v8.0.86
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nalshya113) than the most recent previously approved version (wengliang95) on 2026-03-05, but nalshya113 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.
v6.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.8
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (heartyoh) than the most recent previously approved version (nalshya113) on 2026-03-29, but heartyoh 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.