npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@civilization/lesscoder

v0.1.12

Published

LessCoder CLI wrapper for Code-Native Engine MVP

Downloads

59

Readme

lesscoder

Code-Native Engine for local AI-assisted coding workflows.

This repository provides an end-to-end loop:

Analyze -> Plan -> Execute -> Verify -> Done

Core Modules

  • ALSP (Rust): repository map, symbol lookup, LSP fallback
  • ALSP_ADAPTER (Rust): local protocol service over TCP
  • Patchlet (Rust): atomic Search/Replace patch apply with backup and rollback
  • Orchestrator (Python): LangGraph-based pipeline and repair routing
  • CLI (lesscoder): run tasks, query trace, start server

Requirements

  • Python 3.11+
  • Java 17+
  • Maven 3.9+
  • Rust toolchain (development/source mode only)

Install

After package publish:

pip install lesscoder
npm i -g @civilization/lesscoder

From source (development):

pip install -e .

The npm package is a CLI wrapper that invokes the Python runtime.

Windows x64 install path now uses hybrid adapter resolution:

  • prefer prebuilt adapter from architecture package:
    • PyPI: lesscoder-adapter-win-x64
    • npm: @civilization/lesscoder-adapter-win32-x64 (optional dependency)
  • fallback to cache and GitHub Release download when architecture package is unavailable

lesscoder server runtime mode:

  • Dev mode: if local Rust manifest exists, use cargo run.
  • Installed mode: if no manifest, resolve adapter binary from:
    • LESSCODER_ADAPTER_BIN
    • installed architecture package binary (Windows x64)
    • bundled binary (if packaged)
    • local cache ~/.lesscoder/adapter/...
    • GitHub Release auto-download (default repo: civilization-os/less-coder)
    • checksum verify via lesscoder_adapter_manifest.json when available

Run

lesscoder warmup --project-root /abs/path/to/your/repo
lesscoder server --host 127.0.0.1 --port 8787
lesscoder run --project-root /abs/path/to/your/repo
lesscoder trace --trace-id <trace_id>
lesscoder release-dry-run --project-root /abs/path/to/your/repo --tag v0.1.0

warmup requires explicit path parameters (--project-root or --manifest-path). server can start without project path, then accept system.warmup(project_root=...) later.

MCP Setup

Start the service first:

lesscoder server --host 127.0.0.1 --port 8787

When server starts, it prints:

  • a ready-to-copy MCP config JSON snippet
  • HTTP inspect endpoints:
    • http://127.0.0.1:8787/health
    • http://127.0.0.1:8787/methods

Then configure your MCP client to launch lesscoder as a local server process. Example config (common mcpServers format):

{
  "mcpServers": {
    "lesscoder": {
      "command": "lesscoder",
      "args": ["mcp", "--adapter-host", "127.0.0.1", "--adapter-port", "8787"]
    }
  }
}

Notes:

  • lesscoder mcp is stdio MCP mode (for OpenCode / IDE MCP clients).
  • project activation is explicit via system.warmup payload (project_root/path).
  • If port 8787 is already occupied, change it in both server args and client settings.
  • Current adapter endpoint is 127.0.0.1:<port> with local protocol v0.
  • Browser inspection endpoints are best-effort diagnostics; MCP calls still use local protocol v0.
  • You can override adapter binary path with LESSCODER_ADAPTER_BIN.

Quick Validation

pytest -q tests/integration

Language Status

  • Java: available now
  • Go / JavaScript / TypeScript / C / C++: planned next

Documentation

  • Project guide: PROJECT_GUIDE.md
  • Docs index: docs/README.md
  • Java runtime guide: docs/Java_Runtime_Guide.md
  • Local protocol: docs/local_protocol_v0.md
  • Worklog index: WORKLOG/README.md