← Home

@reifydb/client

npm Repository Homepage
27
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

ddymke

Keywords

reifydbdatabasewebsocketclienttypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Publish workflow change (removed prepublishOnly) explains missing gitHead; no malicious indicators present. ai
phantom-deps phantom-dep:uuid AI (phantom-deps): uuid is a declared runtime dep; phantom-dep heuristic likely misses indirect import patterns in this ESM package. ai
bogus-package bogus-package AI (bogus-package): Sparse README is typical for early-stage monorepo packages; not indicative of spam or malice given consistent versioning and repo. ai

Versions (showing 27 of 27)

Version Deps Published
0.8.1 3 / 5
0.8.0 3 / 5
0.7.0 3 / 5
0.6.0 3 / 5
0.5.6 3 / 5
0.5.0 3 / 5
0.4.13 3 / 5
0.4.12 3 / 5
0.4.11 3 / 5
0.4.10 3 / 5
0.4.9 3 / 5
0.4.8 3 / 5
0.4.7 3 / 5
0.4.6 3 / 5
0.4.2 3 / 5
0.4.1 3 / 5
0.4.0 3 / 5
0.3.0 3 / 5
0.2.0 3 / 5
0.1.7 3 / 5
0.1.6 3 / 5
0.1.5 3 / 5
0.1.4 3 / 5
0.1.3 3 / 5
0.1.2 3 / 5
0.1.1 3 / 5
0.1.0 3 / 5

v0.8.1

1 finding
LOW No provenance attestation provenance

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

v0.8.0

1 finding
LOW No provenance attestation provenance

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

v0.7.0

1 finding
LOW No provenance attestation provenance

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