@tactfulai/ucx-sdk
Tactful AI UCX SDK
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:rollup | AI (phantom-deps): Rollup is referenced in build config (rollup -c); declared-but-not-imported is expected. | ai | |
| phantom-deps | phantom-dep:@tactfulai/auth | AI (phantom-deps): Same-org dep likely re-exported or dynamically loaded; stable FP for this SDK. | ai | |
| phantom-deps | phantom-dep:@tactfulai/ai-sdk | AI (phantom-deps): Same-org dep likely re-exported or dynamically loaded; stable FP for this SDK. | ai | |
| phantom-deps | phantom-dep:@tactfulai/erp-sdk | AI (phantom-deps): Same-org dep likely re-exported or dynamically loaded; stable FP for this SDK. | ai | |
| phantom-deps | phantom-dep:@tactfulai/channels | AI (phantom-deps): Same-org dep likely re-exported or dynamically loaded; stable FP for this SDK. | ai | |
| phantom-deps | phantom-dep:@tactfulai/tenant-sdk | AI (phantom-deps): Same-org dep likely re-exported or dynamically loaded; stable FP for this SDK. | ai | |
| phantom-deps | phantom-dep:@tactfulai/attachments-sdk | AI (phantom-deps): Same-org dep likely re-exported or dynamically loaded; stable FP for this SDK. | ai | |
| phantom-deps | phantom-dep:@tactfulai/livechat-client | AI (phantom-deps): Same-org dep likely re-exported or dynamically loaded; stable FP for this SDK. | ai | |
| phantom-deps | phantom-dep:@tactfulai/automation-client | AI (phantom-deps): Same-org dep likely re-exported or dynamically loaded; stable FP for this SDK. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 9.2.69 | 10 / 11 | |
| 9.2.68 | 10 / 11 | |
| 9.2.67 | 10 / 11 | |
| 9.2.66 | 10 / 11 | |
| 9.2.65 | 10 / 11 | |
| 9.2.64 | 10 / 11 | |
| 9.2.63 | 10 / 11 | |
| 9.2.62 | 10 / 11 | |
| 9.2.61 | 10 / 11 | |
| 9.2.60 | 10 / 11 | |
| 9.2.59 | 10 / 11 | |
| 9.2.58 | 10 / 11 | |
| 9.2.57 | 10 / 11 | |
| 9.2.56 | 10 / 11 | |
| 9.2.55 | 10 / 11 | |
| 9.2.54 | 10 / 11 | |
| 9.2.53 | 10 / 11 | |
| 9.2.52 | 10 / 11 | |
| 9.2.51 | 10 / 11 | |
| 9.2.50 | 9 / 11 | |
| 9.2.21 | 8 / 11 | |
| 9.2.19 | 8 / 11 | |
| 9.2.18 | 9 / 11 | |
| 9.2.17 | 8 / 11 |
v9.2.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.