← Home

@privateaim/server-http-kit

This package contains the realtime application which connects the API with socket based clients.

5
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 gitHead linked

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

tada5hi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Part of @privateaim monorepo; sparse metadata is a quality issue, not a security signal for this publisher. ai
provenance no-provenance AI (provenance): Consistent across all versions of this package; publisher has clean track record. ai
phantom-deps phantom-dep:hapic AI (phantom-deps): hapic is declared as a runtime dependency in package.json; phantom-dep is a false positive here. ai

Versions (showing 5 of 5)

Version Deps Published
0.8.39 20 / 4
0.8.29 20 / 4
0.8.25 20 / 4
0.8.22 20 / 4
0.8.20 20 / 4

v0.8.39

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.

v0.8.29

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.

v0.8.25

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.

v0.8.22

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.

v0.8.20

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.