@things-factory/resource-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@things-factory/auth-ui | AI (dependencies): Same-org sibling package within the @things-factory ecosystem; consistent pattern across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Established @things-factory org package; no provenance is consistent across all versions of this package family. | ai | |
| phantom-deps | phantom-dep:@operato/layout | AI (phantom-deps): Monorepo peer dependency pattern; not directly imported but used via config/re-export. | ai | |
| phantom-deps | phantom-dep:@things-factory/form-ui | AI (phantom-deps): Same-org monorepo dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@things-factory/i18n-base | AI (phantom-deps): Same-org monorepo dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@things-factory/import-ui-csv | AI (phantom-deps): Same-org monorepo dep; indirect import pattern is stable for this package. | ai | |
| phantom-deps | phantom-dep:@things-factory/context-ui | AI (phantom-deps): Same-org monorepo dep; indirect import pattern is stable for this package. | ai | |
| phantom-deps | phantom-dep:@things-factory/resource-base | AI (phantom-deps): Same-org monorepo dep; indirect import pattern is stable for this package. | ai | |
| phantom-deps | phantom-dep:@things-factory/auth-ui | AI (phantom-deps): Same-org monorepo dep; indirect import pattern is stable for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 9.2.19 | 10 / 0 | |
| 9.0.0 | 10 / 0 | |
| 8.0.63 | 10 / 0 | |
| 4.3.823 | 9 / 0 | |
| 4.3.815 | 9 / 0 | |
| 4.3.790 | 9 / 0 | |
| 4.3.764 | 9 / 0 | |
| 4.3.755 | 9 / 0 | |
| 4.3.752 | 9 / 0 | |
| 4.3.743 | 9 / 0 | |
| 4.3.738 | 9 / 0 | |
| 4.3.729 | 9 / 0 | |
| 4.3.689 | 9 / 0 |
v9.2.19
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.
v8.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.823
1 findingPackage 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.790
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.764
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.755
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.752
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.743
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.738
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.729
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.689
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.