@farcaster/snap-hono
Hono integration for Farcaster Snap servers
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-tlds | AI (semgrep): farcaster.xyz is the official Farcaster domain; hardcoded in UI HTML, not a C2/exfiltration endpoint. | ai |
Versions (showing 51 of 65)
| Version | Deps | Published |
|---|---|---|
| 2.1.16 | 3 / 6 | |
| 2.1.15 | 3 / 6 | |
| 2.1.14 | 3 / 6 | |
| 2.1.13 | 3 / 6 | |
| 2.1.12 | 3 / 6 | |
| 2.1.11 | 3 / 6 | |
| 2.1.10 | 3 / 6 | |
| 2.1.9 | 3 / 6 | |
| 2.1.8 | 3 / 6 | |
| 2.1.5 | 3 / 6 | |
| 2.1.4 | 3 / 6 | |
| 2.1.3 | 3 / 6 | |
| 2.1.2 | 3 / 6 | |
| 2.1.1 | 3 / 6 | |
| 2.1.0 | 3 / 6 | |
| 2.0.6 | 3 / 6 | |
| 2.0.5 | 3 / 6 | |
| 2.0.4 | 3 / 6 | |
| 2.0.3 | 3 / 6 | |
| 2.0.2 | 3 / 6 | |
| 2.0.1 | 3 / 6 | |
| 2.0.0 | 3 / 6 | |
| 1.6.0 | 3 / 6 | |
| 1.5.12 | 3 / 6 | |
| 1.5.11 | 3 / 6 | |
| 1.5.10 | 3 / 6 | |
| 1.5.9 | 3 / 6 | |
| 1.5.8 | 3 / 6 | |
| 1.5.7 | 3 / 6 | |
| 1.5.6 | 3 / 6 | |
| 1.5.5 | 3 / 6 | |
| 1.5.4 | 3 / 6 | |
| 1.5.3 | 3 / 6 | |
| 1.5.2 | 3 / 6 | |
| 1.5.1 | 3 / 6 | |
| 1.5.0 | 3 / 6 | |
| 1.4.11 | 3 / 6 | |
| 1.4.10 | 3 / 6 | |
| 1.4.9 | 3 / 6 | |
| 1.4.8 | 3 / 6 | |
| 1.4.7 | 3 / 6 | |
| 1.4.6 | 3 / 6 | |
| 1.4.5 | 3 / 6 | |
| 1.4.4 | 3 / 6 | |
| 1.4.3 | 3 / 6 | |
| 1.4.2 | 3 / 6 | |
| 1.4.1 | 3 / 6 | |
| 1.4.0 | 3 / 6 | |
| 1.3.3 | 3 / 6 | |
| 1.3.2 | 3 / 6 | |
| 1.3.1 | 3 / 6 |
v2.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (grinio) than the most recent previously approved version (bob-neynar) on 2026-04-04, but grinio 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.
v1.4.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (grinio) than the most recent previously approved version (bob-neynar) on 2026-04-04, but grinio 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.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.