← Home

@walletconnect/heartbeat

npm Repository Homepage

HeartBeat

5
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

cyberdrknachosanhuxwellchris13524devcelinegancho_walletconnectbkrempedrouid

Keywords

timetimestamptesttestinglabelunit testing

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:chai AI (phantom-deps): Test tooling misplaced in deps, used via config not direct import. ai
phantom-deps phantom-dep:mocha AI (phantom-deps): Test tooling misplaced in deps, used via config not direct import. ai
phantom-deps phantom-dep:ts-node AI (phantom-deps): Test tooling misplaced in deps, used via config not direct import. ai
bogus-package bogus-package AI (bogus-package): Part of WalletConnect monorepo; inflated semver reflects coordinated versioning, sparse README is typical for internal ecosystem utilities. ai
dependencies unvetted-dep:@walletconnect/time AI (dependencies): @walletconnect/time is a sibling package from the same WalletConnect monorepo; not a third-party risk. ai

Versions (showing 5 of 5)

Version Deps Published
1.2.2 3 / 4
1.2.1 3 / 6
1.2.0 6 / 6
1.0.1 3 / 6
1.0.0 2 / 7

v1.2.0

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: bkrem → gancho_walletconnect (on 2023-01-16, known maintainer) provenance

This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (bkrem) on 2023-01-16, but gancho_walletconnect 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.

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

v1.0.0

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.