@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish env variance for trusted internal publisher; no malicious indicator. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party @tactfulai package, not third-party. | 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:rollup | AI (phantom-deps): Rollup is referenced in build config (rollup -c); declared-but-not-imported is expected. | 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 | |
| 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/auth | AI (phantom-deps): Same-org dep likely re-exported or dynamically loaded; stable FP for this SDK. | ai |
Versions (showing 51 of 59)
| Version | Deps | Published |
|---|---|---|
| 9.2.74 | 10 / 11 | |
| 9.2.73 | 10 / 11 | |
| 9.2.72 | 10 / 11 | |
| 9.2.71 | 10 / 11 | |
| 9.2.70 | 10 / 11 | |
| 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.49 | 9 / 11 | |
| 9.2.48 | 9 / 11 | |
| 9.2.47 | 9 / 11 | |
| 9.2.46 | 9 / 11 | |
| 9.2.45 | 9 / 11 | |
| 9.2.44 | 9 / 11 | |
| 9.2.43 | 9 / 11 | |
| 9.2.42 | 9 / 11 | |
| 9.2.41 | 9 / 11 | |
| 9.2.40 | 9 / 11 | |
| 9.2.39 | 9 / 11 | |
| 9.2.38 | 9 / 11 | |
| 9.2.37 | 9 / 11 | |
| 9.2.36 | 9 / 11 | |
| 9.2.35 | 9 / 11 | |
| 9.2.34 | 9 / 11 | |
| 9.2.33 | 9 / 11 | |
| 9.2.32 | 9 / 11 | |
| 9.2.31 | 9 / 11 | |
| 9.2.30 | 9 / 11 | |
| 9.2.29 | 9 / 11 | |
| 9.2.28 | 9 / 11 | |
| 9.2.27 | 9 / 11 | |
| 9.2.26 | 8 / 11 | |
| 9.2.25 | 8 / 11 | |
| 9.2.24 | 8 / 11 |
v9.2.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.49
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.48
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.47
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.46
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.45
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.44
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.43
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.42
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.41
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.40
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.39
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.38
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.37
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.36
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.35
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.34
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.33
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.32
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.31
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.30
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.29
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.28
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.27
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.26
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.25
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.24
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tactfulai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.