@tactfulai/livechat-client
26
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
tactfulai
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@tactful/common | AI (dependencies): Same-org rename of existing dependency, not a new third party. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Rename/rescope of existing dep, not an added attack surface. | ai | |
| provenance | missing-githead | AI (provenance): Likely a one-off publish environment change; no other risk signals present and publisher has clean history. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; no provenance is common and not a risk indicator here. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 3.0.22 | 2 / 2 | |
| 3.0.21 | 2 / 2 | |
| 3.0.20 | 2 / 2 | |
| 3.0.19 | 2 / 2 | |
| 3.0.18 | 2 / 2 | |
| 3.0.17 | 2 / 2 | |
| 3.0.16 | 2 / 2 | |
| 3.0.15 | 2 / 2 | |
| 3.0.14 | 2 / 2 | |
| 3.0.13 | 2 / 2 | |
| 3.0.12 | 2 / 2 | |
| 3.0.11 | 2 / 2 | |
| 3.0.10 | 2 / 2 | |
| 3.0.9 | 2 / 2 | |
| 3.0.8 | 2 / 2 | |
| 3.0.7 | 2 / 2 | |
| 3.0.6 | 2 / 2 | |
| 3.0.5 | 2 / 2 | |
| 3.0.4 | 2 / 2 | |
| 3.0.3 | 2 / 2 | |
| 3.0.1 | 2 / 2 | |
| 3.0.0 | 2 / 2 | |
| 2.0.6 | 2 / 2 | |
| 2.0.5 | 2 / 2 | |
| 2.0.4 | 2 / 2 | |
| 2.0.0 | 2 / 2 |
v3.0.22
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.21
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.