lurqrun 0.0.1 → 0.0.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -8,93 +8,33 @@ lurq is a **companion to your coding agent**: it recommends and explains package
8
8
 
9
9
  ---
10
10
 
11
- ## quick start (dev)
11
+ ## quick start: connect your agent
12
12
 
13
- ```bash
14
- npm install
15
- cp .env.example .env
16
- docker compose up -d
17
- npm run build
18
- npx lurqrun --help
19
- ```
13
+ > **not public yet.** lurq unlocks at launch. [join the waitlist](https://lurq.run); the steps below are how it'll work once it's live.
20
14
 
21
- ## development
15
+ lurq is a **hosted service**: you don't run a database or a sync. get an API key,
16
+ then run the guided installer:
22
17
 
23
18
  ```bash
24
- npm run dev -- <command>
25
- npm test
26
- npm run typecheck
27
- npm run lint
19
+ npx lurqrun install
28
20
  ```
29
21
 
30
- ## configuration
31
-
32
- see [`.env.example`](./.env.example). only `DATABASE_URL` is required;
33
- gitHub/openAI keys allow full access to lurq commands but are not strictly necessary.
34
-
35
- | var | required | purpose |
36
- |---|---|---|
37
- | `DATABASE_URL` | yes | postgres connection (pgvector-enabled) |
38
- | `GITHUB_TOKEN` | recommended | github signals (stars, cadence, issues, archived) |
39
- | `EMBEDDING_PROVIDER` / `EMBEDDING_API_KEY` | no | openai embeddings; falls back to a local embedder |
40
- | `SUMMARY_PROVIDER` / `SUMMARY_API_KEY` | no | llm usage guides; falls back to the npm description |
41
-
42
- ## setup the index
43
-
44
- ```bash
45
- npx lurqrun db migrate # create schema (pgvector) + load the curated seed list
46
- npx lurqrun sync # scores from public APIs (~2 min)
47
- ```
48
-
49
- `sync` is idempotent and tolerant of single-source outages. run it on a schedule
50
- (default frequency: daily) to keep the index fresh.
51
-
52
- ## cli usage
53
-
54
- ```bash
55
- npx lurqrun recommend "a form library for react"
56
- npx lurqrun recommend "debounce a function"
57
- npx lurqrun evaluate zod
58
- npx lurqrun compare drizzle-orm prisma typeorm
59
- npx lurqrun verify lodahs
60
- ```
22
+ it prompts for your key, validates it, detects your installed assistants
23
+ (Claude Code, Cursor, Windsurf, VS Code/Copilot, Codex), and writes a keyed
24
+ remote MCP entry:
25
+ `{ "type": "http", "url": "https://api.lurq.run/mcp", "headers": { "Authorization": "Bearer …" } }`.
26
+ **no database credentials ever touch your machine.** restart your agent afterward.
61
27
 
62
- add `--json` to any command for machine output; `--category` and `--min-confidence`
63
- filter `recommend`.
28
+ ## what your agent gets (mcp tools)
64
29
 
65
- ## mcp tools
66
-
67
- `npx lurqrun serve` starts the MCP server (stdio). it exposes:
68
-
69
- - **`recommend`** — best current packages for a described need (≤5, scored, with confidence)
70
- - **`evaluate`** — full evidence read for one package (scores, advisories, usage guide)
71
- - **`compare`** — 2–5 packages ranked by health
72
- - **`verify`** — is a package real, healthy, and not risky? (anti-hallucination guard)
73
- - **`diagram`** — a reference-architecture mermaid diagram for a stack (optional)
74
-
75
- every response is compact and carries a `dataAsOf` timestamp.
76
-
77
- ## install into your agent
78
-
79
- ```bash
80
- npx lurqrun install-skill --agent claude-code # or cursor | windsurf | copilot | codex | all
81
- ```
82
-
83
- merges a `lurq` MCP server entry into the agent's config (never overwriting other
84
- config) and drops a short instructions file telling the agent when to call lurq.
85
- restart the agent afterward.
86
-
87
- ## how it works
88
-
89
- ```
90
- public APIs (npm, github, deps.dev, bundlephobia)
91
- → ingestion → scoring (+ confidence) → summaries/usage guides → embeddings
92
- → postgres + pgvector
93
- → { mcp server, cli }
94
- ```
30
+ once installed, the agent can call these tools over MCP. every response is
31
+ compact and carries a `dataAsOf` timestamp.
95
32
 
96
- scores are computed from public signals never hand-written. confidence
97
- labels (`proven` / `emerging` / `unproven`) reflect the strength of discovered evidence
33
+ - **`recommend`**: best current packages for a described need (≤5, scored, with confidence)
34
+ - **`evaluate`**: full evidence read for one package (scores, advisories, usage guide)
35
+ - **`compare`**: 2 to 5 packages ranked by health
36
+ - **`verify`**: is a package real, healthy, and not risky? (anti-hallucination guard)
37
+ - **`diagram`**: a reference-architecture mermaid diagram for a stack (optional)
98
38
 
99
39
  ## outreach
100
40