← Home

@fre4x/exa

npm

An MCP server for Exa.ai (formerly Metaphor) search.

10
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

fritzprix

Keywords

mcpexametaphorsearchai

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:koa AI (typosquat): Scoped package @fre4x/exa is an Exa.ai MCP server; Levenshtein match to 'koa' is coincidental noise. ai
typosquat typosquat.levenshtein:next AI (typosquat): Scoped package @fre4x/exa is an Exa.ai MCP server; Levenshtein match to 'next' is coincidental noise. ai
phantom-deps phantom-dep:zod AI (phantom-deps): zod is a declared runtime dep; likely used in compiled dist output, not directly imported in TS source. ai
phantom-deps phantom-dep:axios AI (phantom-deps): axios is a declared runtime dep; likely used in compiled dist output, not directly imported in TS source. ai

Versions (showing 10 of 10)

Version Deps Published
1.1.0 3 / 4
1.0.65 3 / 4
1.0.64 3 / 4
1.0.61 3 / 4
1.0.60 3 / 4
1.0.58 3 / 4
1.0.57 3 / 4
1.0.55 3 / 4
1.0.54 3 / 4
1.0.53 3 / 4

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.65

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.

v1.0.64

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.

v1.0.61

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.

v1.0.60

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.

v1.0.58

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.

v1.0.57

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.

v1.0.55

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.

v1.0.54

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.

v1.0.53

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.