← Home

@farcaster/auth-client

npm Repository Homepage
8
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

sdstopocount_neynarmcilroyc-neynargrinioshreyas_chorgebob-neynarneynar_matthewvarunsrindaddeotybook-neynarmanan-neynar

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Manual publish by known maintainer, not a compromised pipeline. ai
maintainer-change maintainer-added AI (maintainer-change): Publisher is a known, long-track-record maintainer; churn is organizational. ai
publish-pattern new-deps-added AI (publish-pattern): viem is a well-known, established dependency replacing siwe. ai

Versions (showing 8 of 8)

Version Deps Published
0.7.1 2 / 0
0.7.0 2 / 0
0.6.0 2 / 0
0.5.0 2 / 0
0.4.0 2 / 2
0.3.0 2 / 2
0.2.1 2 / 2
0.2.0 2 / 2

v0.6.0

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: daddeo.

LOW No provenance attestation provenance

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

INFO Publisher changed: ecm_merkle → daddeo (on 2025-05-19, known maintainer) provenance

This version was published by a different npm account (daddeo) than the most recent previously approved version (ecm_merkle) on 2025-05-19, but daddeo 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.

v0.5.0

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: daddeo.

LOW No provenance attestation provenance

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

INFO Publisher changed: ecm_merkle → daddeo (on 2025-05-12, known maintainer) provenance

This version was published by a different npm account (daddeo) than the most recent previously approved version (ecm_merkle) on 2025-05-12, but daddeo 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.

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.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.

v0.2.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.