← Home

@farcaster/hub-nodejs

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

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

sdstopocount_neynarmcilroyc-neynargrinioshreyas_chorgebob-neynarneynar_matthewvarunsrindaddeotybook-neynarmanan-neynar

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@noble/hashes AI (phantom-deps): @noble/hashes is explicitly declared as a runtime dependency in package.json; phantom-dep is a false positive here. ai

Versions (showing 14 of 14)

Version Deps Published
0.16.0 4 / 3
0.15.9 4 / 3
0.15.8 4 / 3
0.15.7 4 / 3
0.15.6 4 / 3
0.15.5 4 / 3
0.15.4 4 / 3
0.15.3 4 / 3
0.15.2 4 / 3
0.15.1 4 / 3
0.15.0 4 / 3
0.14.1 4 / 3
0.14.0 4 / 3
0.13.6 4 / 3

v0.16.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.15.9

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: sanjayprabhu → aditiharini (on 2025-10-13, known maintainer) provenance

This version was published by a different npm account (aditiharini) than the most recent previously approved version (sanjayprabhu) on 2025-10-13, but aditiharini 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.15.8

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: sanjayprabhu → aditiharini (on 2025-09-30, known maintainer) provenance

This version was published by a different npm account (aditiharini) than the most recent previously approved version (sanjayprabhu) on 2025-09-30, but aditiharini 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.15.7

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: aditiharini → sanjayprabhu (on 2025-09-15, known maintainer) provenance

This version was published by a different npm account (sanjayprabhu) than the most recent previously approved version (aditiharini) on 2025-09-15, but sanjayprabhu 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.15.6

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: aditiharini → sanjayprabhu (on 2025-08-29, known maintainer) provenance

This version was published by a different npm account (sanjayprabhu) than the most recent previously approved version (aditiharini) on 2025-08-29, but sanjayprabhu 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.15.5

1 finding
LOW No provenance attestation provenance

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

v0.15.4

1 finding
LOW No provenance attestation provenance

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

v0.15.3

1 finding
LOW No provenance attestation provenance

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

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

v0.15.1

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: sanjayprabhu → aditiharini (on 2025-06-25, known maintainer) provenance

This version was published by a different npm account (aditiharini) than the most recent previously approved version (sanjayprabhu) on 2025-06-25, but aditiharini 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.15.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.

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

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