← Home

@bddh/starling-realtime-client

npm Repository Homepage
9
Versions
MIT
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

jtarchjazzysnailsanxycoderdctgongdongaliyah666

Keywords

reactindexDB

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:uuid AI (phantom-deps): Declared in both peerDependencies and dependencies; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:lodash AI (phantom-deps): Declared in both peerDependencies and dependencies; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:@bddh/starling-brtc AI (phantom-deps): Declared in both peerDependencies and dependencies; same-org monorepo pattern. ai
phantom-deps phantom-dep:@bddh/starling-json AI (phantom-deps): Declared in both peerDependencies and dependencies; same-org monorepo pattern. ai
phantom-deps phantom-dep:@bddh/starling-cutout AI (phantom-deps): Declared in both peerDependencies and dependencies; same-org monorepo pattern. ai
phantom-deps phantom-dep:@bddh/starling-web-socket AI (phantom-deps): Declared in both peerDependencies and dependencies; same-org monorepo pattern. ai
phantom-deps phantom-dep:@bddh/starling-timeout-controller AI (phantom-deps): Declared in both peerDependencies and dependencies; same-org monorepo pattern. ai

Versions (showing 9 of 9)

Version Deps Published
2.0.13 7 / 0
2.0.8 7 / 0
2.0.7 7 / 0
2.0.6 7 / 0
2.0.5 7 / 0
2.0.4 7 / 0
2.0.3 7 / 0
2.0.2 7 / 0
2.0.1 7 / 0

v2.0.13

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: gongdong → aliyah666 (on 2026-05-25, known maintainer) provenance

This version was published by a different npm account (aliyah666) than the most recent previously approved version (gongdong) on 2026-05-25, but aliyah666 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.0.8

1 finding
LOW No provenance attestation provenance

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

v2.0.7

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.

v2.0.6

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.

v2.0.5

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.

v2.0.4

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.

v2.0.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.

v2.0.2

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.

v2.0.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.