@things-factory/worklist
Module to manage the todo list of business participants
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Long-established package; lack of provenance is consistent across all prior versions and is not a risk signal here. | ai | |
| dependencies | unvetted-dep:@operato/graphql | AI (dependencies): Same-org ecosystem dependency from hatiolab; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@operato/event-view | AI (dependencies): Same-org ecosystem dependency from hatiolab; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@operato/grist-editor | AI (dependencies): Same-org ecosystem dependency from hatiolab; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@things-factory/shell | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@things-factory/board-ui | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@things-factory/auth-base | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@things-factory/context-ui | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@operato/moment-timezone-es | AI (dependencies): Same-org ecosystem dependency from hatiolab; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@operato/p13n | AI (dependencies): Same-org ecosystem dependency from hatiolab; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@things-factory/board-service | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@things-factory/attachment-base | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@things-factory/personalization | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@things-factory/scheduler-client | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions. | ai | |
| phantom-deps | phantom-dep:@operato/moment-timezone-es | AI (phantom-deps): Referenced in config files per analyzer note; not a real phantom dep concern. | ai | |
| phantom-deps | phantom-dep:@things-factory/board-service | AI (phantom-deps): Same-org sibling; indirect usage pattern is normal for this monorepo. | ai | |
| phantom-deps | phantom-dep:@things-factory/personalization | AI (phantom-deps): Same-org sibling; indirect usage pattern is normal for this monorepo. | ai | |
| dependencies | unvetted-dep:@things-factory/organization | AI (dependencies): Same-org monorepo sibling; stable pattern across all versions. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 9.2.24 | 15 / 0 | |
| 9.2.19 | 15 / 0 | |
| 9.1.0 | 15 / 0 | |
| 9.0.41 | 15 / 0 | |
| 9.0.35 | 15 / 0 | |
| 9.0.34 | 15 / 0 | |
| 9.0.33 | 15 / 0 | |
| 9.0.32 | 15 / 0 | |
| 9.0.28 | 15 / 0 | |
| 9.0.27 | 15 / 0 | |
| 9.0.26 | 15 / 0 | |
| 9.0.25 | 15 / 0 | |
| 9.0.24 | 15 / 0 | |
| 9.0.20 | 15 / 0 | |
| 9.0.19 | 15 / 0 | |
| 9.0.15 | 15 / 0 | |
| 9.0.14 | 15 / 0 | |
| 9.0.13 | 15 / 0 | |
| 9.0.12 | 15 / 0 | |
| 9.0.6 | 15 / 0 | |
| 9.0.5 | 15 / 0 | |
| 9.0.4 | 15 / 0 | |
| 9.0.2 | 15 / 0 | |
| 9.0.1 | 15 / 0 | |
| 9.0.0 | 15 / 0 |
v9.2.24
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.35
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.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.26
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.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.6
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.4
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.1
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.