← Home

@tokenflight/api

HTTP clients for Hyperstream and Fiat APIs

17
Versions
Apache-2.0
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

jaydenxtannr

Keywords

apicross-chaindefifiathyperstreamtokenflight

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:hapi AI (typosquat): Scoped @tokenflight/api package; no plausible impersonation of hapi — different namespace and purpose. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped package with clear brand identity; not a typosquat of pg. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package with clear brand identity; not a typosquat of joi. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped package with clear brand identity; not a typosquat of ajv. ai

Versions (showing 17 of 17)

Version Deps Published
0.4.5 1 / 4
0.4.4 1 / 5
0.4.3 1 / 5
0.4.2 1 / 5
0.4.1 1 / 5
0.4.0 1 / 3
0.3.1 1 / 3
0.3.0 1 / 3
0.2.3 1 / 3
0.2.2 1 / 3
0.2.1 1 / 3
0.2.0 1 / 3
0.1.4 1 / 3
0.1.3 1 / 3
0.1.2 1 / 3
0.1.1 1 / 3
0.1.0 1 / 3

v0.4.5

1 finding
LOW No provenance attestation provenance

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

v0.4.4

1 finding
LOW No provenance attestation provenance

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

v0.4.3

1 finding
LOW No provenance attestation provenance

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

v0.4.2

1 finding
LOW No provenance attestation provenance

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