@sylphx/locus

Name: @sylphx/locus
Author: io.github.SylphxAI

MCPcommunity

v0.6.1io.github.SylphxAIUnknownUpdated todaynpm GitHub

Locus — the exact code chunk for the job: local hybrid code search for agents.

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

12GitHub stars

5Forks

todayLast update

Package

Authorio.github.SylphxAI

LicenseUnknown

Version0.6.1

Sourcenpm+mcp-registry

npm@sylphx/locus

GitHubSylphxAI/locus

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 21 resolved+ · none vulnerable

Tool surface—

Security scan✓ Cleanv0.6.1 · todayHow well does this scan work?

EvalsNone

IndexedSep 23, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source17h ago

Forge read 8 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Locus — the exact code chunk for the job: local hybrid code search for agents.

Keywords

mcp

Alternatives

Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-23 — observed resolution, not a publisher declaration.

21 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

@sylphx/coderag0.2.05 dependencies
- ignore7.0.10
- drizzle-orm0.45.3
- @sylphx/synth0.1.3
- @libsql/client0.14.05 dependencies
  - libsql0.4.72 dependencies
    detect-libc2.0.2
    @neon-rs/load0.0.4
  - js-base643.9.4
  - @libsql/core0.14.01 dependency
    js-base643.9.4shown above
  - promise-limit2.7.0
  - @libsql/hrana-client0.7.04 dependencies
    js-base643.9.4shown above
    node-fetch3.3.2incomplete
    @libsql/isomorphic-ws0.1.5incomplete
    @libsql/isomorphic-fetch0.3.1
- @parcel/watcher2.6.04 dependencies
  - detect-libc2.1.2
  - is-glob4.0.31 dependency
    is-extglob2.1.1
  - node-addon-api7.1.1
  - picomatch4.0.7

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

Declared but not resolved

5 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

below the depth cap: 5

data-uri-to-buffer ^4.0.0 — required by node-fetch@3.3.2below the depth cap
fetch-blob ^3.1.4 — required by node-fetch@3.3.2below the depth cap
formdata-polyfill ^4.0.10 — required by node-fetch@3.3.2below the depth cap
ws ^8.13.0 — required by @libsql/isomorphic-ws@0.1.5below the depth cap
@types/ws ^8.5.4 — required by @libsql/isomorphic-ws@0.1.5below the depth cap

Not followed: optionalDependencies, peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.