@things-factory/offline-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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): horwengliang95 is an established publisher in the same org with 237 approved packages; transition appears legitimate. | ai | |
| provenance | no-provenance | AI (provenance): Long-lived monorepo package; no provenance is consistent across all versions in this org. | ai | |
| phantom-deps | phantom-dep:@things-factory/layout-base | AI (phantom-deps): Same-org sibling dependency; phantom-dep heuristic unreliable for monorepo peer deps. | ai | |
| phantom-deps | phantom-dep:@operato/layout | AI (phantom-deps): Monorepo package; deps referenced in config files rather than direct imports is expected pattern. | ai | |
| phantom-deps | phantom-dep:@things-factory/i18n-base | AI (phantom-deps): Same-org monorepo dependency; indirect usage via config is expected. | ai | |
| phantom-deps | phantom-dep:@things-factory/offline-base | AI (phantom-deps): Same-org monorepo dependency; indirect usage via config is expected. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 9.2.33 | 3 / 0 | |
| 9.2.30 | 3 / 0 | |
| 9.2.29 | 3 / 0 | |
| 9.2.24 | 3 / 0 | |
| 9.2.19 | 3 / 0 | |
| 9.2.17 | 3 / 0 | |
| 9.2.16 | 3 / 0 | |
| 9.2.13 | 3 / 0 | |
| 9.2.5 | 3 / 0 | |
| 9.1.19 | 3 / 0 | |
| 9.1.13 | 3 / 0 | |
| 9.1.0 | 3 / 0 | |
| 9.0.41 | 3 / 0 | |
| 9.0.36 | 3 / 0 | |
| 9.0.34 | 3 / 0 | |
| 9.0.25 | 3 / 0 | |
| 9.0.24 | 3 / 0 | |
| 9.0.20 | 3 / 0 | |
| 9.0.5 | 3 / 0 | |
| 9.0.2 | 3 / 0 | |
| 9.0.0 | 3 / 0 | |
| 8.0.88 | 3 / 0 | |
| 8.0.87 | 3 / 0 | |
| 8.0.86 | 3 / 0 | |
| 8.0.75 | 3 / 0 | |
| 8.0.74 | 3 / 0 | |
| 8.0.64 | 3 / 0 | |
| 8.0.63 | 3 / 0 | |
| 6.4.10 | 3 / 0 | |
| 6.4.8 | 3 / 0 | |
| 4.3.815 | 3 / 0 | |
| 4.3.767 | 3 / 0 | |
| 4.3.764 | 3 / 0 | |
| 4.3.755 | 3 / 0 | |
| 4.3.752 | 3 / 0 | |
| 4.3.743 | 3 / 0 | |
| 4.3.740 | 3 / 0 | |
| 4.3.738 | 3 / 0 | |
| 4.3.734 | 3 / 0 | |
| 4.3.729 | 3 / 0 | |
| 4.3.727 | 3 / 0 | |
| 4.3.725 | 3 / 0 | |
| 4.3.723 | 3 / 0 | |
| 4.3.705 | 3 / 0 | |
| 4.3.695 | 3 / 0 | |
| 4.3.689 | 3 / 0 |
v9.2.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.24
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.