← Home

@farcaster/core

npm Repository Homepage
17
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
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped @farcaster/core is a legitimate Farcaster protocol package, not a typosquat of cors. ai

Versions (showing 17 of 17)

Version Deps Published
0.19.0 6 / 9
0.18.11 6 / 9
0.18.10 6 / 9
0.18.9 6 / 9
0.18.8 6 / 9
0.18.7 6 / 9
0.17.1 6 / 9
0.17.0 6 / 9
0.16.5 6 / 9
0.16.4 6 / 9
0.16.3 6 / 9
0.16.2 6 / 9
0.16.1 6 / 9
0.16.0 6 / 9
0.15.6 6 / 9
0.15.5 6 / 9
0.15.4 6 / 9

v0.16.4

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

1 finding
LOW No provenance attestation provenance

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

v0.16.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.16.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 → 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.16.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: aditiharini → 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 (aditiharini) 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.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 → 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 (aditiharini) 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.15.5

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

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.