@things-factory/document-template-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/form-ui | AI (dependencies): Same-org monorepo dependency; stable pattern across this package's versions. | ai | |
| dependencies | unvetted-dep:@things-factory/grist-ui | AI (dependencies): Same-org monorepo dependency replacing @operato/data-grist; routine intra-org swap. | ai | |
| provenance | no-provenance | AI (provenance): Established @things-factory org package; provenance not used across this ecosystem. | ai | |
| phantom-deps | phantom-dep:@things-factory/utils | AI (phantom-deps): Same-org monorepo dep; phantom detection is a false positive for this package structure. | ai | |
| phantom-deps | phantom-dep:@things-factory/document-template-base | AI (phantom-deps): Same-org monorepo dep; phantom detection is a false positive for this package structure. | ai | |
| phantom-deps | phantom-dep:@things-factory/styles | AI (phantom-deps): Same-org monorepo dep; phantom detection is a false positive for this package structure. | ai | |
| phantom-deps | phantom-dep:@things-factory/i18n-base | AI (phantom-deps): Same-org monorepo dep; phantom detection is a false positive for this package structure. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 9.2.24 | 7 / 0 | |
| 9.2.19 | 7 / 0 | |
| 9.2.17 | 7 / 0 | |
| 9.1.0 | 7 / 0 | |
| 9.0.41 | 7 / 0 | |
| 9.0.36 | 7 / 0 | |
| 9.0.34 | 7 / 0 | |
| 9.0.25 | 7 / 0 | |
| 9.0.24 | 7 / 0 | |
| 9.0.20 | 7 / 0 | |
| 9.0.5 | 7 / 0 | |
| 9.0.2 | 7 / 0 | |
| 9.0.0 | 7 / 0 | |
| 8.0.88 | 7 / 0 | |
| 8.0.87 | 7 / 0 | |
| 8.0.64 | 7 / 0 | |
| 8.0.63 | 7 / 0 | |
| 4.3.695 | 7 / 0 | |
| 4.3.689 | 7 / 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.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.17
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 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.24
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.0.20
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.0.5
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.0.2
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.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.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.695
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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.