@things-factory/setting-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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@things-factory/styles | AI (phantom-deps): Same-org scope; typical for framework packages with shared styles. | ai | |
| phantom-deps | phantom-dep:@operato/layout | AI (phantom-deps): Monorepo pattern; operato packages are framework dependencies used transitively. | ai | |
| phantom-deps | phantom-dep:@things-factory/utils | AI (phantom-deps): Same-org scope; typical for framework packages with shared utilities. | ai | |
| phantom-deps | phantom-dep:@things-factory/more-base | AI (phantom-deps): Same-org scope; typical for framework packages with shared base. | ai | |
| phantom-deps | phantom-dep:@things-factory/form-ui | AI (phantom-deps): Same-org scope; typical for framework packages with shared components. | ai | |
| phantom-deps | phantom-dep:@things-factory/i18n-base | AI (phantom-deps): Same-org scope; typical for framework packages with shared i18n. | ai | |
| provenance | no-provenance | AI (provenance): Long-lived ecosystem package; provenance not used across the things-factory monorepo consistently. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 9.2.19 | 14 / 0 | |
| 9.1.13 | 14 / 0 | |
| 9.1.0 | 14 / 0 | |
| 9.0.41 | 14 / 0 | |
| 9.0.36 | 14 / 0 | |
| 9.0.34 | 14 / 0 | |
| 9.0.25 | 14 / 0 | |
| 9.0.24 | 14 / 0 | |
| 9.0.20 | 14 / 0 | |
| 9.0.5 | 14 / 0 | |
| 9.0.2 | 14 / 0 | |
| 9.0.0 | 14 / 0 | |
| 4.3.695 | 9 / 0 | |
| 4.3.689 | 9 / 0 |
v9.2.19
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 (horwengliang95) on 2026-04-28, 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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.695
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.689
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.