← Home

@evergonlabs/tmi-protocol-api-client

npm

> **DEPRECATED:** This package is deprecated. Use `@evergonlabs/tmi-protocol-api/client` instead. > > ```ts > import { buildClients, parseResponse } from "@evergonlabs/tmi-protocol-api/client"; > > const clients = buildClients("http://localhost:3000"); >

42
Versions
MIT
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

feraudetrajajaevergonlabs-npm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Deprecated package with long history; missing provenance is acceptable here. ai

Versions (showing 42 of 42)

Version Deps Published
0.22.2 2 / 12
0.22.1 2 / 12
0.22.0 2 / 12
0.21.5 2 / 12
0.21.4 2 / 12
0.21.3 2 / 12
0.21.2 2 / 12
0.21.1 2 / 12
0.21.0 2 / 12
0.19.0 2 / 14
0.18.1 2 / 14
0.18.0 2 / 14
0.17.1 2 / 14
0.16.7 2 / 14
0.16.6 2 / 14
0.16.5 2 / 14
0.16.4 2 / 14
0.16.3 2 / 14
0.16.2 2 / 14
0.16.1 2 / 14
0.16.0 2 / 14
0.15.2 2 / 14
0.15.1 2 / 14
0.15.0 2 / 14
0.14.4 2 / 14
0.14.3 2 / 14
0.14.2 2 / 14
0.14.1 2 / 14
0.14.0 2 / 14
0.13.2 2 / 14
0.4.10 2 / 14
0.4.9 1 / 15
0.4.8 1 / 15
0.4.7 1 / 15
0.4.6 2 / 14
0.4.5 2 / 14
0.4.4 1 / 15
0.4.3 1 / 15
0.4.2 2 / 14
0.4.0 1 / 11
0.3.2 1 / 11
0.3.1 1 / 11

v0.4.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.3

2 findings
MEDIUM Publisher changed: ivan_k → atapin (on 2025-03-10, unremoved on npm for 495d) provenance

This version was published by a different npm account (atapin) than the most recent previously approved version (ivan_k) on 2025-03-10. It has since remained available on npm for 495 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.2

2 findings
MEDIUM Publisher changed: ivan_k → atapin (on 2025-03-10, unremoved on npm for 495d) provenance

This version was published by a different npm account (atapin) than the most recent previously approved version (ivan_k) on 2025-03-10. It has since remained available on npm for 495 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ivan_k.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.