← Home

@farcaster/hub-nodejs

npm Repository Homepage
42
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
provenance publisher-changed AI (provenance): Manual-to-CI/CD attested migration, improved provenance not a compromise signal. ai
maintainer-change maintainer-removed AI (maintainer-change): Old maintainers removed as part of same legitimate handoff. ai
maintainer-change maintainer-added AI (maintainer-change): Long-standing publisher change, stable on npm 687d, no malicious content in diff. ai
provenance publisher-changed-stale AI (provenance): Publisher change unremoved for 687d, consistent with legitimate transfer. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy explained by unchanged content diff; no malicious behavior found. ai
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 42 of 42)

Version Deps Published
0.16.0 4 / 3
0.15.11 4 / 3
0.15.10 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
0.13.5 4 / 3
0.13.4 4 / 3
0.13.3 4 / 3
0.13.2 4 / 3
0.13.1 4 / 3
0.13.0 4 / 3
0.12.7 4 / 3
0.12.6 4 / 3
0.12.5 4 / 3
0.12.4 4 / 3
0.12.3 4 / 3
0.12.2 4 / 3
0.12.1 4 / 3
0.12.0 4 / 3
0.11.24 4 / 3
0.11.23 4 / 3
0.11.22 4 / 3
0.11.21 4 / 3
0.11.20 4 / 3
0.11.19 4 / 3
0.11.18 4 / 3
0.11.17 4 / 3
0.11.16 4 / 3
0.11.15 4 / 3
0.11.14 4 / 3
0.11.13 4 / 3

v0.13.5

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 → sds (on 2025-05-07, known maintainer) provenance

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

1 finding
LOW No provenance attestation provenance

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

v0.13.3

1 finding
LOW No provenance attestation provenance

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

v0.13.2

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 → caheart_mm (on 2025-04-28, known maintainer) provenance

This version was published by a different npm account (caheart_mm) than the most recent previously approved version (sanjayprabhu) on 2025-04-28, but caheart_mm 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.13.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: caheart_mm → sanjayprabhu (on 2025-04-14, known maintainer) provenance

This version was published by a different npm account (sanjayprabhu) than the most recent previously approved version (caheart_mm) on 2025-04-14, 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.13.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: caheart_mm → sanjayprabhu (on 2025-04-04, known maintainer) provenance

This version was published by a different npm account (sanjayprabhu) than the most recent previously approved version (caheart_mm) on 2025-04-04, 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.12.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: sanjayprabhu → caheart_mm (on 2024-10-28, known maintainer) provenance

This version was published by a different npm account (caheart_mm) than the most recent previously approved version (sanjayprabhu) on 2024-10-28, but caheart_mm 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.12.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 2024-10-16, known maintainer) provenance

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

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 2024-10-14, known maintainer) provenance

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

1 finding
LOW No provenance attestation provenance

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

v0.12.3

2 findings
MEDIUM Publisher changed: sanjayprabhu → caheart_mm (on 2024-09-17, unremoved on npm for 669d) provenance

This version was published by a different npm account (caheart_mm) than the most recent previously approved version (sanjayprabhu) on 2024-09-17. It has since remained available on npm for 669 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v0.12.2

2 findings
MEDIUM Publisher changed: sanjayprabhu → caheart_mm (on 2024-08-30, unremoved on npm for 687d) provenance

This version was published by a different npm account (caheart_mm) than the most recent previously approved version (sanjayprabhu) on 2024-08-30. It has since remained available on npm for 687 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v0.12.1

1 finding
LOW No provenance attestation provenance

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

v0.12.0

1 finding
LOW No provenance attestation provenance

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

v0.11.24

1 finding
LOW No provenance attestation provenance

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

v0.11.23

1 finding
LOW No provenance attestation provenance

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

v0.11.22

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: wazzymandias → sanjayprabhu (on 2024-07-27, known maintainer) provenance

This version was published by a different npm account (sanjayprabhu) than the most recent previously approved version (wazzymandias) on 2024-07-27, 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.11.21

1 finding
LOW No provenance attestation provenance

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

v0.11.20

1 finding
LOW No provenance attestation provenance

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

v0.11.19

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 → wazzymandias (on 2024-06-30, known maintainer) provenance

This version was published by a different npm account (wazzymandias) than the most recent previously approved version (sanjayprabhu) on 2024-06-30, but wazzymandias 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.11.18

1 finding
LOW No provenance attestation provenance

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

v0.11.17

1 finding
LOW No provenance attestation provenance

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

v0.11.16

1 finding
LOW No provenance attestation provenance

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

v0.11.15

1 finding
LOW No provenance attestation provenance

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

v0.11.14

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

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.