← Home

@1sat/connect

npm

Connection layer for 1Sat wallet - popup flow, events, session management

26
Versions
MIT
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

dcasegrwildsatchmo

Keywords

1satbsvordinalswalletsdkconnect

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:dist/index.js AI (source-diff): Long Base58 string is a hardcoded BSV BEEF transaction used as a test fixture in throwDummyReviewActions; not obfuscated malware. ai
phantom-deps phantom-dep:eventemitter3 AI (phantom-deps): eventemitter3 is a declared runtime dep; phantom-dep heuristic fires because it's not directly imported in analyzed entry points. ai

Versions (showing 26 of 26)

Version Deps Published
0.0.84 4 / 2
0.0.83 4 / 2
0.0.82 4 / 2
0.0.81 4 / 2
0.0.79 4 / 2
0.0.78 4 / 2
0.0.77 4 / 2
0.0.76 4 / 2
0.0.75 4 / 2
0.0.74 4 / 2
0.0.72 4 / 2
0.0.71 4 / 2
0.0.70 4 / 2
0.0.69 4 / 2
0.0.67 4 / 2
0.0.65 4 / 2
0.0.64 4 / 2
0.0.62 4 / 2
0.0.53 4 / 2
0.0.8 1 / 1
0.0.7 1 / 1
0.0.6 1 / 1
0.0.5 1 / 1
0.0.3 1 / 1
0.0.2 1 / 1
0.0.1 1 / 1

v0.0.84

1 finding
LOW No provenance attestation provenance

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

v0.0.83

1 finding
LOW No provenance attestation provenance

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

v0.0.82

1 finding
LOW No provenance attestation provenance

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

v0.0.81

1 finding
LOW No provenance attestation provenance

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

v0.0.79

1 finding
LOW No provenance attestation provenance

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

v0.0.78

1 finding
LOW No provenance attestation provenance

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

v0.0.77

1 finding
LOW No provenance attestation provenance

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

v0.0.76

1 finding
LOW No provenance attestation provenance

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

v0.0.75

1 finding
LOW No provenance attestation provenance

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

v0.0.74

1 finding
LOW No provenance attestation provenance

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

v0.0.72

1 finding
LOW No provenance attestation provenance

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

v0.0.71

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: wildsatchmo → dcasegr (on 2026-07-11, known maintainer) provenance

This version was published by a different npm account (dcasegr) than the most recent previously approved version (wildsatchmo) on 2026-07-11, but dcasegr 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.