← Home

@neynar/react

npm

Farcaster frontend React component library powered by Neynar

12
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

manan-neynarshreyaschorgelucas-neynarrishmbob-neynar

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): env-spread is in vite.config.ts (build tooling only); does not affect published runtime bundle or consumer secrets. ai
phantom-deps phantom-dep:mipd AI (phantom-deps): mipd is a declared runtime dependency; phantom-dep heuristic is a false positive here. ai
phantom-deps phantom-dep:hls.js AI (phantom-deps): hls.js is a declared runtime dependency; phantom-dep heuristic is a false positive here. ai

Versions (showing 12 of 12)

Version Deps Published
1.2.22 2 / 33
1.2.21 3 / 32
1.2.20 2 / 33
1.2.12 4 / 31
1.2.8 4 / 31
1.2.7 4 / 31
1.2.6 4 / 31
1.2.5 2 / 33
1.2.4 2 / 33
1.2.3 0 / 35
1.2.2 0 / 35
1.2.1 0 / 35

v1.2.22

2 findings
HIGH env-spread: vite.config.ts:29 semgrep

Spreading entire process.env into an object — may capture all secrets 27 | ], 28 | define: { > 29 | "process.env": { 30 | ...process.env, 31 | SDK_VERSION: JSON.stringify(SDK_VERSION),

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.

v1.2.21

1 finding
LOW No provenance attestation provenance

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

v1.2.20

2 findings
HIGH env-spread: vite.config.ts:29 semgrep

Spreading entire process.env into an object — may capture all secrets 27 | ], 28 | define: { > 29 | "process.env": { 30 | ...process.env, 31 | SDK_VERSION: JSON.stringify(SDK_VERSION),

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.

v1.2.12

2 findings
HIGH env-spread: vite.config.ts:29 semgrep

Spreading entire process.env into an object — may capture all secrets 27 | ], 28 | define: { > 29 | "process.env": { 30 | ...process.env, 31 | SDK_VERSION: JSON.stringify(SDK_VERSION),

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.

v1.2.8

1 finding
LOW No provenance attestation provenance

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

v1.2.7

1 finding
LOW No provenance attestation provenance

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

v1.2.6

1 finding
LOW No provenance attestation provenance

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

v1.2.5

2 findings
HIGH env-spread: vite.config.ts:29 semgrep

Spreading entire process.env into an object — may capture all secrets 27 | ], 28 | define: { > 29 | "process.env": { 30 | ...process.env, 31 | SDK_VERSION: JSON.stringify(SDK_VERSION),

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.

v1.2.4

2 findings
HIGH env-spread: vite.config.ts:29 semgrep

Spreading entire process.env into an object — may capture all secrets 27 | ], 28 | define: { > 29 | "process.env": { 30 | ...process.env, 31 | SDK_VERSION: JSON.stringify(SDK_VERSION),

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.

v1.2.3

2 findings
HIGH env-spread: vite.config.ts:29 semgrep

Spreading entire process.env into an object — may capture all secrets 27 | ], 28 | define: { > 29 | "process.env": { 30 | ...process.env, 31 | SDK_VERSION: JSON.stringify(SDK_VERSION),

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.

v1.2.2

2 findings
HIGH env-spread: vite.config.ts:29 semgrep

Spreading entire process.env into an object — may capture all secrets 27 | ], 28 | define: { > 29 | "process.env": { 30 | ...process.env, 31 | SDK_VERSION: JSON.stringify(SDK_VERSION),

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.

v1.2.1

2 findings
HIGH env-spread: vite.config.ts:29 semgrep

Spreading entire process.env into an object — may capture all secrets 27 | ], 28 | define: { > 29 | "process.env": { 30 | ...process.env, 31 | SDK_VERSION: JSON.stringify(SDK_VERSION),

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.