← Home

@api.global/typedsocket

npm
6
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

lossless

Keywords

WebSocketType SafetyReal-time CommunicationClient-Server ArchitectureTypeScriptNetworking

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@push.rocks/smartdelay AI (dependencies): Same @push.rocks org; added as part of routine refactor replacing smartsocket. ai
dependencies unvetted-dep:@push.rocks/smartjson AI (dependencies): Same Lossless GmbH org as the publisher; consistent ecosystem dependency across versions. ai
dependencies unvetted-dep:@push.rocks/smartstring AI (dependencies): Same Lossless GmbH org as the publisher; consistent ecosystem dependency across versions. ai
provenance no-provenance AI (provenance): Lossless GmbH packages consistently lack provenance; stable false positive for this publisher. ai

Versions (showing 6 of 6)

Version Deps Published
4.1.4 8 / 8
4.1.3 9 / 8
4.1.2 9 / 8
4.1.0 9 / 8
4.0.0 8 / 8
3.1.1 8 / 8

v4.1.4

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: lossless.

INFO No provenance attestation provenance

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

v4.1.3

1 finding
LOW No provenance attestation provenance

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

v4.1.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.

v4.1.0

1 finding
INFO No provenance attestation provenance

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

v4.0.0

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.1.1

1 finding
LOW No provenance attestation provenance

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